>From: "Adam Taylor" <address@hidden> >Organization: ULM >Keywords: 200411031957.iA3JuxvV029184 McIDAS ADDE Adam, >There is a firewall on our main campus, that is why you cannot telnet. OK, there is also a firewall setup on cyclone that does not allow access through ports McIDAS ADDE uses. >The output from telnet is a bunch of mcservsh line (something) setenv: >command not found I missed this when I glanced at the .mcenv in ~mcidas. the settings in the file must be in Bourne/Korn shell syntax: address@hidden ~]$ cat .mcenv # Bourne/Korn shell '.mcenv' environment variable definitions for the user # 'mcadde' # umask umask 002 I see that someone changed these to be in Cshell syntax: # MCHOME setenv MCHOME /home/mcidas ... I changed these back to Bourne/Korn shell syntax, so the error about 'setenv command not found' will disappear. >I am using Mcidas MCGUI. OK. I see client routing table setup in the /home/mcidas/data/ADDESITE.TXT file. You are using the local ADDE interface for some datasets and the remote one for others: ADDE_ROUTE_RTWXTEXT=LOCAL-DATA ADDE_ROUTE_RTGRIDS=LOCAL-DATA ADDE_ROUTE_AMRC=LOCAL-DATA ADDE_ROUTE_CIMSS=LOCAL-DATA ADDE_ROUTE_GINICOMP=LOCAL-DATA ADDE_ROUTE_GINIEAST=LOCAL-DATA ADDE_ROUTE_GINIWEST=LOCAL-DATA ADDE_ROUTE_ME7=LOCAL-DATA ADDE_ROUTE_RTNEXRAD=LOCAL-DATA ADDE_ROUTE_TOPO=LOCAL-DATA ADDE_ROUTE_MYDATA=LOCAL-DATA ADDE_ROUTE_GOESEAST=LOCAL-DATA ADDE_ROUTE_RTIMAGES=CYCLONE.GEOS.ULM.EDU ADDE_ROUTE_RTPTSRC=CYCLONE.GEOS.ULM.EDU ADDE_ROUTE_NEXRCOMP=CYCLONE.GEOS.ULM.EDU HOST_CYCLONE.GEOS.ULM.EDU=127.0.0.1 After undoing the Cshell syntax additions to .mcenv, I can list out data from the remote ADDE interface on cyclone: address@hidden ~/workdata]$ imglist.k RTIMAGES/GE-IR.ALL Image file directory listing for:RTIMAGES/GE-IR Pos Satellite/ Date Time Center Band(s) sensor Lat Lon --- ------------- ------------ -------- ---- ---- ------------ 1 G-12 IMG 1 NOV 04306 01:15:00 0 72 4 2 G-12 IMG 1 NOV 04306 01:45:00 0 72 4 ... This works because localhost is allowed total access to the ports McIDAS ADDE can/will use. It will not work if the same access is tried from a different machine in your same domain or any other machine accessible by the Internet. If you want your remote ADDE server to be accessible from an machine other than cyclone, you will need to open up access through ports 112, 500, and 503. >The ADDE error I get with IDV is "Input not in compress format". I did >install compress and uncompress. (didn't realize they were not installed) >still did not fix the problem. The setup in the 'mcidas' account is now set to use 'gzip' compressed data transfers. I am not sure what the default for IDV is (although I think that the default is to use 'gzip' compressed transfers), but the problem you were seeing may have been caused by two different things: - the error in .mcenv - compress and uncompress not being found (not likely if the default for IDV is to use gzip transfers) >Using the MCGUI I can SEE the data sets and says that I have images >available but when I try to open them in either MCGUI or IDV(from ADDE), I >get nothing showing up in MCGUI and IDV says there are no data sets. The only thing I can think of here is that you did listings for datasets that were accessible through LOCAL-DATA access, and you tried to display images from a dataset(s) that the client routing table had setup to use remote ADDE access: LOCAL-DATA access datasets from /home/mcidas/data/ADDESITE.TXT: ADDE_ROUTE_RTWXTEXT=LOCAL-DATA ADDE_ROUTE_RTGRIDS=LOCAL-DATA ADDE_ROUTE_AMRC=LOCAL-DATA ADDE_ROUTE_CIMSS=LOCAL-DATA ADDE_ROUTE_GINICOMP=LOCAL-DATA ADDE_ROUTE_GINIEAST=LOCAL-DATA ADDE_ROUTE_GINIWEST=LOCAL-DATA ADDE_ROUTE_ME7=LOCAL-DATA ADDE_ROUTE_RTNEXRAD=LOCAL-DATA ADDE_ROUTE_TOPO=LOCAL-DATA ADDE_ROUTE_MYDATA=LOCAL-DATA ADDE_ROUTE_GOESEAST=LOCAL-DATA remote ADDE access datasets from /home/mcidas/data/ADDESITE.TXT: ADDE_ROUTE_RTIMAGES=CYCLONE.GEOS.ULM.EDU ADDE_ROUTE_RTPTSRC=CYCLONE.GEOS.ULM.EDU ADDE_ROUTE_NEXRCOMP=CYCLONE.GEOS.ULM.EDU I strongly recommend that, after you verify that you can access images in say the RTIMAGES dataset, that you change access in McIDAS to the remote ADDE interface: DATALOC ADD RTWXTEXT CYCLONE.GEOS.ULM.EDU DATALOC ADD RTGRIDS CYCLONE.GEOS.ULM.EDU DATALOC ADD CIMSS CYCLONE.GEOS.ULM.EDU DATALOC ADD GINICOMP CYCLONE.GEOS.ULM.EDU DATALOC ADD GINIEAST CYCLONE.GEOS.ULM.EDU DATALOC ADD GINIWEST CYCLONE.GEOS.ULM.EDU and DATALOC ADD AMRC AMRC.SSEC.WISC.EDU DATALOC ADD GOESEAST UNIDATA2.SSEC.WISC.EDU This makes setting up non-mcidas user accounts a snap. IDV will use the remote ADDE access, so fixing the problem in .mcenv should allow it to access the datasets that were setup. The only other thing I can add about the MCGUI is you must start a session that has at least 17 frames since single image loads are done in frame 11. I must add that the error in .mcenv would be a show stopper for all access to the remote ADDE intervace on cyclone. >I used >menu Information and then data availability and it shows me that there are >images there. However neither MCGUI or IDV(using ADDE) can see them. > >I just can't seem to figure out what is the heck is going on. As far as I >know I have everytime set up correctly. But apparently something is still >screwed up. >HELP!!! It looks like one problem was in .mcenv. The next problem you will face is the firewall setup on cyclone. I can change this to what we use here in the UPC if you like. Please let me know. >Thanks No worries. Cheers, Tom -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us. >From address@hidden Thu Nov 4 16:41:28 2004 The entire thing seems to be working now. IDV can see all data sets and so can mcidas. It was the .mcenv that was causing the problems. I got confused when the .mcenv was in the korn/Bourne shell but my account was in the C shell. That's why I changed it. Woops!! Thanks a ton Adam Taylor
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.