You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that this is a pretty minor issue, but I've noticed that PRIDE does not always handle file paths with spaces well. For example, I have an external drive with spaces in the drive name 'my\ drive', however, if I attempt to run the test scripts, PRIDE fails to find the config tables located on the drive due to the file path. I think this problem affects the paths read from the config file in particular, because if I try to point PRIDE toward manually downloaded satellite products, I get a similar problem.
The text was updated successfully, but these errors were encountered:
Thanks for your feedback. I guess you are using the Windows version? Actually, a blank in the file path will potentially cause problems that can hardly be prevented or precautioned. For safety and convenience of software maintenance, we regulated that no blanks should appear in the file path.
I am using a Mac, but that is good to know that there should not be any blanks in file paths. There are some ways of handling them, but it would likely take some time to go through the code and make the necessary changes.
I know that this is a pretty minor issue, but I've noticed that PRIDE does not always handle file paths with spaces well. For example, I have an external drive with spaces in the drive name 'my\ drive', however, if I attempt to run the test scripts, PRIDE fails to find the config tables located on the drive due to the file path. I think this problem affects the paths read from the config file in particular, because if I try to point PRIDE toward manually downloaded satellite products, I get a similar problem.
The text was updated successfully, but these errors were encountered: