McIDAS-V Support Forums

Great! I'm glad you were able to get your script running using cron.

Bob

Great! I'm glad to hear that my suggestion appears to be working well. Please let me know if you have any further questions.

Thanks,
Bob

Thanks for the explanation, that sounds like a good justification for writing the AREAs locally. I think my suggestion of running background scripts to write the AREAs might be the easiest solution for this, especially if you want things to run without much user interaction of if you plan on updatin...

Hello, There is no simple way of doing what you are suggesting. Is there any reason why you need the AREAs locally and can't work directly off of the remote server/dataset? Please note that the advice below might be useful if you have familiarity with Python scripting, especially in McIDAS-V. If I u...

Hello, This seems to work on Windows 10, but I replicated your error on macOS. I wrote this up as inquiry 2995 . I did find a way to get this working though. Here are the steps: Load your data source as normal. Display your data as normal. In the Layer Controls tab of the Data Explorer, select "...

Hello, While we are actively working on the 1.9 release, I don't yet have an estimate on when it will be released. However, I noticed that I actually can create GFS global 1 degree soundings in the core 1.8 build. See this image: soundings.png There are two "Sounding Data (with true winds)"...

Hello, This is actually an issue that has been fixed in the McIDAS-V 1.9beta1 nightly build, which you can download here . The login and password for the page are both: mcv Please note that the nightly builds include any code changes from the previous day, and therefore not everything has been fully...

Hi Yunus, I'm replicating the problem of the map lines being hidden behind the data using a 2D map panel if I zoom in close enough to the data. Zoomed out, the map lines appear on top of the data for me. I wrote this up as inquiry 2993 . Sometimes this can happen in standard 3D map display panels as...

Hello, I'm glad you were able to come up with workarounds for some of your problems. I decided to keep inquiries 2988 and 2989 open as I feel that these are both good suggestions and there may be more general solutions to them other than creating a new projection. I added mention of your workaround ...

Hello, When loaded through the HYDRA chooser, McIDAS-V sets the min/max enhancement values based on the min/max of the data in the scene. When loaded through ADDE, McIDAS-V uses a parameter default to display the data with a range of 180 - 320K. You can see statistical information about the data obj...