Familiar McIDAS-X style (hopefully) to display images

[joleenf]

I removed my original scripts since the scripting methods for McIDAS-V have developed to the point that my scripts are not necessary. Please refer to the scripting section of the McIDAS-V user's guide.

Once again to Jon and Mike: Great work, I am looking forward to more new scripting methods!

Joleen

[joleenf]

A reference to previous information removed.

[kbedka1]

wow, this looks like great stuff! Can these be run on a remote machine?

[joleenf]

Kris,

I need to begin running on a remote machine because my computer does not always have internet access and is not running 24/7. I have heard that there are some extra needs when running remotely. To the McIDAS Support Staff: do I need any special tools to allow me to run my scripts on a remote machine and save some images?

Thanks,
Joleen

[Rick]

Hi Joleen,

If you don't have internet access, you could not run something remotely on another workstation. So am I assuming correctly you want to use cronjob on a remote to schedule a McV background process? If that is the case, you'll need to look into using xvfb and create a virtual display. I'll try to write this up as a thread under tricks and tips, but as a start, you can look at the following inquiry.

http://mcidas.ssec.wisc.edu/inquiry-v/?inquiry=184

If that's not the case, let me know.

[joleenf]

Thanks Rick, that is what I meant. I will look at the inquiry.

Joleen

[joleenf]

Rick,

I don't know what I am doing with setting up the virtual machine. I believe I have it set up, but when I try to run McV, I get

I am lost on this one. I have Xvfb running(?) on display 2. I export display 2 to my machine, try running McV and get... I can't run the prefs or config to change the heap space.

[joleenf@flash McIDAS-V-System]$ . ./runMcV
dirname: invalid option -- b
Try `dirname --help' for more information.
Reading system configuration...
mcv flags: -Dvisad.java3d.textureNpot=true -Dvisad.java3d.imageByRef=true -Dvisad.java3d.geometryByRef=true -Didv.3d=true -Didv.sysmem=16047 -userpath /home/joleenf/McIDAS-V
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

I can't run the config to change the heap space options.

Joleen

[kbedka1]

Joleen:

Did Bao's post help you at all?

viewtopic.php?f=31&t=984&start=10

[joleenf]

Kris,

I am not having any luck setting up the virtual display for an interactive session. However, I understand that as long as setOffScreen(1) is set, I should not need to run a virtual display. I watched Rick run successfully with setOffScreen(1), but have not had the same results on my mac. I have not been able to get anything running on the remote linux box.

This is the error that I am getting with that

/home/joleenf/McIDAS-V-System/runMcV -pyfile $HOME/mcidas/scripts/callImgDisp.py
Reading system configuration...
mcv flags: -Dvisad.java3d.textureNpot=true -Dvisad.java3d.imageByRef=true -Dvisad.java3d.geometryByRef=true -Didv.3d=true -Didv.sysmem=16047 -userpath /home/joleenf/McIDAS-V
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

setOffScreen(1) has been added at the beginning of callImgDisp.py.

This is the IDV documentation for setOffScreen
http://www.unidata.ucar.edu/software/id ... onISL.html

Joleen

[tomw]

This message:
"Could not reserve enough space for object heap"
indicates to me that the machine on which you are trying to run this does not have enough memory to support the start-up of McV. Can you do a "runMcV" from the command line and see what the -Xmx value is?