Importing large SIMM file

[Kyle Chadwick]

I am trying to import SIMM files that I created to opensim. It creates the opensim file but when its open it is extremely lagg-y and wont load the screen or controls properly. I suspect this is because the file is so large (6,843 KB). Is there anything I could do, apart from purchasing more RAM for my computer?

Thanks,
Kyle

[Ayman Habib]

Hi Kyle,

Although the osim file format (xml) is a bit more verbose due to XML tags (so the file size is bigger) but the contents are relatively similar to SIMM files. I've never seen a model that's too big to cause the behavior you describe, and we imported full body models among others. Maybe it would help if you import the bodies (jnt file) separately then do both jnt and msl files to help pinpoint/isolate the problem object(s). I suspect it's a bug rather than just a large model. Any rough numbers for the number of bodies, joints, muscles and markers? Any constraints in the model, as these tend to slow down initial assembly.

Best regards,
-Ayman

[Kyle Chadwick]

Thank you Ayman,

I tried importing just the jnt file and everything appeared to work fine, so the issue must be in the msl file. The main issue remains that the Navigator, Coordinates, and Properties windows are blank (with just the jnt file loaded, these all function properly). Any idea what could be wrong with the msl file? this is my general format for them:

beginmuscle muscle3_4d
begingroups
msls_radial4
endgroups
beginpoints
50.77 32.77 9.00 segment ground
0.00 11.11 0.02 segment seg1_4
0.00 7.18 0.02 segment seg2_4
0.00 3.49 0.50 segment seg3_4
endpoints
endmuscle

There are about 1115 joints, 1115 bones, and 2230 muscles (0-25 wrapping points per muscle).

Thanks,
Kyle

[Ayman Habib]

Hi Kyle,

I have to admit that I didn't use models with that many segments/joints/muscles. I'm curious what you're modeling and if indeed you need this level of details or you can simplify your model instead as most of the user interface has not been optimized to handle models of this size (e.g. coordinate panel and navigator are slow and you'd be scrolling continuously).

This aside, I don't expect that the code will break or fail merely due to the size. Maybe you can take out the wrapping first, if the problem persists do with only fewer muscles. If this's a display problem (likely muscles related) it may help to "hide" some or all the muscles and see if the performance improves.

Please let me know how it goes.

-Ayman

[Kyle Chadwick]

Thank you for your troubleshooting advice, Ayman. I have tried it with just 41 muscles now (with no wrapping points) and aside from a slow graphics window, everything shows up. This leads me to believe there is an issue with size (or complexity).

fyi, the model is of a single cownose ray fin (with accurate # and placement of cartilege elements), so simplifying would defeat the purpose of the study.

Thanks,
Kyle

[Ayman Habib]

Hi Kyle,

I'd be interested to try this model out on one of our newer/beefed-up machines to see if there's a bug or if it's a matter of resources and possibly provide some suggestions. Please feel free to file a bug report and attach the model and I'll pick it up from there.

Thanks,
-Ayman