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

Support relative paths when FTing Schedule:File objects #4865

Closed
shorowit opened this issue Apr 21, 2023 · 0 comments · Fixed by #4879
Closed

Support relative paths when FTing Schedule:File objects #4865

shorowit opened this issue Apr 21, 2023 · 0 comments · Fixed by #4879

Comments

@shorowit
Copy link
Contributor

Enhancement Request

IDF file paths for, e.g., the Schedule:File object end up as absolute paths after Forward Translation. Users download e.g. ResStock End Use Load Profile models, try to run them, and encounter errors because the absolute file paths don't exist on their computer.

It'd be nice if there was a way to preserve relative paths in the IDF. (As far as I can tell, the OS:External:File object does support relative paths, but they do not get maintained in the final IDF.)

It seems like the implementation could:

  1. Add a FT option to use relative paths, or
  2. Preserve the OS:External:File path in the IDF Schedule:File (which allows the user to choose if they want to use relative or absolute paths), or
  3. ???

I'm not sure if the request applies to other objects.

cc @joseph-robertson

@shorowit shorowit added Enhancement Request Triage Issue needs to be assessed and labeled, further information on reported might be needed labels Apr 21, 2023
@tijcolem tijcolem added component - CLI and removed Triage Issue needs to be assessed and labeled, further information on reported might be needed labels May 5, 2023
@DavidGoldwasser DavidGoldwasser added this to the OpenStudio SDK 3.7.0 milestone May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants