Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Save Model with Cloud Storage #615

Open
Ski90Moo opened this issue Jul 24, 2023 · 0 comments
Open

Unable to Save Model with Cloud Storage #615

Ski90Moo opened this issue Jul 24, 2023 · 0 comments
Labels
Enhancement Request New feature or request Triage Issue needs to be assessed and labeled, further information on reported might be needed

Comments

@Ski90Moo
Copy link

Enhancement Request

When the osm model is saved on a cloud storage (such as microsoft onedrive or dropbox), OpenStudio shows an error that it was unable to save the model (and therefore unable to run the simulation). Often, the user must wait until everything is synced before running the simulation. Most of the time it actually does save the file, which causes the cloud drive to sync again, but says it is unable to save and therefore unable to run the simulation.

There have been several instances where, even though it is synced with the cloud drive, it still produces this error and will not run. At this point I must save the file under a new name in order to run the simulation and proceed with modeling.

I do have a custom spreadsheet that links to some of the data in the eplustbl.tab file. When I have the .tab file open, I am unable to run the simulation, so I always must close this file.

Detailed Description

Possible Implementation

@Ski90Moo Ski90Moo added Enhancement Request New feature or request Triage Issue needs to be assessed and labeled, further information on reported might be needed labels Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Request New feature or request Triage Issue needs to be assessed and labeled, further information on reported might be needed
Projects
None yet
Development

No branches or pull requests

1 participant