Openstudio not responding / too long filename

LSurf
487 ●1 ●9

It seemed that running an .osm file from the measures folder created this error. Some loop is created that creates an infinite depth of directories.

So: Never run an .osm-file from the OpenStudio\Measures directory!!

Some loop occurs, recursively creating more and more directories. You'll be unable to delete the directories, since filenames are too long.

To remove these files, you need to use subst from command prompt and assign a drive letter (quite ugly solution, but works). Proceed as follows:

Open a command prompt, and cd into the offending directory until you cannot go further, then go a few directories back up
use subst to assign a drive letter to the offending directory. e.g. subst z: <dirname>
go to z:, and remove all files using del /s /q <dirname>, then rd /s /q <dirname>
In case you still get errors, go deeper in the tree, and assign a new driveletter to an offending directory (i could typically get 20 dirs deep), repeat until you can get to the lowest directory and remove everything. I had to use about 6 driveletter to get to the deepest level.
You may have several branches of offending directories, dig into each until you can remove all.

link

Comments

@LSurf, thanks for the answer. Could you clarify which version of OS you were using as well as what you mean by "Never run an .osm-file from the measures directory"? Are you referring to running an OSM in your "My Measures Directory" using the OpenStudio application? This closed issue is the only one I know of that caused these infinitely deep folders. Is the issue you are referring to or is this something new?

macumber ( 10 years ago )

Thanks for the followup. Perhaps I wasn't very thorough in describing. Also since this fixed the issue for me I didn't investigate further.

Yes, I meant running an .osm file from the my measures directory, and running it from Openstudio (not PAT) I was using this as a test file in debugging my measures, so it made sense to me to place my .osm in the my measures directory. I'm guessing that when the file is run, it makes a copy of the measure to its working directory, which is in the measure directory, therefore creating the loop.

LSurf ( 10 years ago )

I see, so you 1) create a measure, 2) create an osm in that measure, 3) open the osm in OS App, 4) add the measure to the osm using the app. I can see how that could cause problems, I've added this issue.

macumber ( 10 years ago )

Instead of posting these issues here, should I instead file these on github?

LSurf ( 10 years ago )

@LSurf if you are sure that you know what the issue is and how to reproduce it, posting on github is fine. If you are not sure then just post on UH, we can investigate and add issues as needed. Linking to the github issue from UH just let's users see that the issue is logged and follow work on it if they want.

macumber ( 10 years ago )

add a comment