-
Notifications
You must be signed in to change notification settings - Fork 68
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
Error messages when launching uvcdat on Rhea. #727
Comments
I should have noted that uvcdat actually seemed to run fine in spite of these errors. |
We should make sure that all erroneous errors and print statements are removed. Thanks for pointing this out. From: cameronsmith1 <notifications@github.commailto:notifications@github.com> I should have noted that uvcdat actually seemed to run fine in spite of these errors. — |
@cameronsmith1 it would be useful to know what your environment variables look like as the Can you list the output using the following please, just to make sure it's not an issue:
|
Looks like you have slightly old version of CDAT. What SHA you are building? |
he is using yesterday morning build of UV-CDAT on rhea, you're right it's already 24 hours old ;) |
@durack1 he is sourcing the setup_runtime.csh so he can use the command line, but the "Executable" uvcdat resources it. I will post an issue to remind us from unsetting the vars before runnnig uvcdat so we're sure uvcdat GUI is using the correct python. |
I see. I can confirm that these messages I am seeing as well (but in the uvcdatsession.log file) |
@doutriaux1 I agree, unsetting these variables as part of the script would be a good idea.. So that such tangles don't occur at anytime.. Getting this unsetting to work across shells though is going to be a pain, as was the original *.csh edits.. |
The commands I used (from Charles) were: The version I used is 2.0.beta-2337-g32b4249. The output of env | grep PATH is (after the commands above):
|
@doutriaux1 I will clarify my badly made point above. It would be good if the setup scripts checked for existing python/uvcdat paths, and removed other installations.. I agree this would be painful to do, but would also attempt to resolve issues with tangled paths causing users problems in which no coherent error message will easily be able to explain (and consequently the user complains to you about it not working). |
Other than the environment issues, is there a problem with VisTrails's output here? It seems that these messages popping up is the correct behavior here (when using |
moving to 2.1 |
kind of agree with @remram44 print statement should probably be there when using --output="" closing for now. |
The text was updated successfully, but these errors were encountered: