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

path_length #71

Closed
FabienRech opened this issue Feb 1, 2023 · 2 comments
Closed

path_length #71

FabienRech opened this issue Feb 1, 2023 · 2 comments

Comments

@FabienRech
Copy link

Hi,
I was wondering if there is a potential limit to the length of the path directory used by the RTStrcuctBuilder.create_from() ?

I have created a script which was working well but as I lauched it on a new computer (and adapted the path) it did not work...I had no space or special caractere in my path.

The only solution I have found was to change the path by reducing it a little bit ?

Do you have an explanation ?

Best

Fabien

@awtkns
Copy link
Contributor

awtkns commented Feb 1, 2023

HI @FabienRech, I have run into this issue before when working with dicom structures. Assuming you are using windows there is limitation of 260 characters the path length in the files systems. More details can be found here.

The Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character. For example, the maximum path on drive D is "D:\some 256-character path string" where "" represents the invisible terminating null character for the current system codepage. (The characters < > are used here for visual clarity and cannot be part of a valid path string.)

This the is no restriction in RT-utils on path length. @asim-shrestha I believe this can be closed

@FabienRech
Copy link
Author

FabienRech commented Feb 2, 2023

Thank you,
Finally I think I likely did a mistake in one character (inversion of two characters - the devils is in the details) , despite multiple checking in the path....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants