-
Notifications
You must be signed in to change notification settings - Fork 3
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
Local paths in ihm_external_files.file_path #26
Comments
The path is output by PMI with 'correct' path separators, i.e. / on Linux and \ on Windows, so the test needs to be updated to match. What isn't clear is if mmCIF itself allows platform-specific paths, or whether Linux-style paths should be used everywhere. Relates ihmwg/IHMCIF#26.
I assumed in ChimeraX that any relative path in ihm_external_files.file_path was relative to directory containing the ihm file. |
For local supplementary files, the path is relative to master ihm file. I understand restricting to POSIX-like file paths creates problem with Windows builds. We can may be remove that restriction for now. |
It doesn't cause a problem - I just need to know whether to emit paths using |
Yes |
Better I think to always use /. ChimeraX does not know what OS the file was written on so won't know whether to expect / or \.
… On Mar 29, 2017, at 9:52 AM, Ben Webb ***@***.***> wrote:
I understand restricting to POSIX-like file paths creates problem with Windows builds
It doesn't cause a problem - I just need to know whether to emit paths using / or \. By "POSIX-like file paths" do you mean /?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Does
ihm_external_files.file_path
require paths to be separated with/
or\
or is either acceptable? Windows builds of our software will naturally output paths separated with\
while the provided examples all use/
. The docs say "This data item assumes a POSIX-like directory structure" but I'm not sure if that means "you must use / to separate paths".For local files, the path is required to be a relative path. But relative to what?
The text was updated successfully, but these errors were encountered: