McIDAS-V Support Forums

1.7beta1 9-22-2017 Nightly

I think I chose IR temperature first, then anvil, then visible texture rating, then OT Probability. Color-shaded plan view. I did subset the Northern Hemisphere as the Southern Hemisphere GOES data has irregular scanning.

I was not using any formulas or derived fields

No I am not using Adaptive Resolution. I was not happy with the way that feature performed for me in other displays I've made so I disabled it. Here is a sample file I was using:

ftp://ftp.ssec.wisc.edu/pub/incoming/GO ... 2011117.nc

Note that the subset box in the lower right of the Field Selector is performing strangely with this data as well.

I am working with a large dataset in McIDAS-V and I notice that when I eliminate a layer label (i.e. the one that displays at the bottom of a plot) in the display properties, it seems that all data fields displayed are forced to reload. This is an arduous process, for example I have 4 displays, only...

I've remembered this happening throughout my entire time of using McIDAS-V.

here is the file you requested. The computer is brand new so it is very unlikely I am having hardware problems. I have no problems with no other software. This type of problem had occurred on my previous laptop as well as my new one, so I am skeptical that the hardware is causing it.

This just happened to me, I clicked the open a new tab button and the software crashed. Here is the console message about java 8/8/17 10:18:56.710 AM ReportCrash[9878]: Saved crash report for java[7619] version 1.0 (1.0) to /Users/kbedka/Library/Logs/DiagnosticReports/java_2017-08-08-101856_LASLA170...

ftp.ssec.wisc.edu/pub/incoming/nexrad_3d_3_1_20060407T184500Z.nc

I have verified that I am able to load the 89 GHz data through the process you detail. Thank you for the help. I am running into a problem though. I have to use both the vertical (V) and horizontal (H) polarization channels in a formula to get what's called a polarization corrected temperature (PCT)...

I have a 3-D volume of radar data that I want to see an isosurface. If I pick a large reflectivity value, I get reasonable looking results, see attached. When I go to a smaller value which should better show the 3-D structure of the entire storm, I get weird looking results. I recall this was a prob...