This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: "Mekonnen Gebremichael" <address@hidden> >Organization: Pratt School of Engineering, Duke University >Keywords: 200504201601.j3KG1gv2005753 McIDAS probing image values Hi Mekonnen, >Am sorry to get back to you again. Am almost done, so be patient. No worries. >What I did >was copy all the files in one day to "/disk/space/mek11/USdata/GOES/". Then, >I did 'dsserve...". When I did 'imglist IR183/AREA', I could see there are >48 images, as desired. Sounds good. >(1) Then I did.. redirect ADD globir.\* \"/disk/space/mek11/USdata/GOES". It >said "redirect: Done". But when I typed 'damp.k globir.', It only prints >the previous results for '/disk/space/mek11/GOESdatanew'. (assuming that you meant to say redirect.k instead of redirect) the only thing I see wrong with this is the closing quote. I just took the liberty of logging on as you to look at your REDIRECTions. This can be done in two different ways: redirect.k LIST Number of active redirection entries=2 globir.* /disk/space/mek11/GOESdatanew globir.\* /disk/space/mek11/GOESdatanew redirect.k: Done or by looking in the file that is the persistent store for the definitions: cd ~mek11/mcidas/data cat LWPATH.NAM You can see from the redirect.k LIST that the definition you were trying to add was not saved. Given this, I just typed: redirect.k ADD globir.\* \"/disk/space/mek11/USdata/GOES and the result was good: redirect.k: Done sagres% redirect.k LIST Number of active redirection entries=2 globir.* /disk/space/mek11/USdata/GOES globir.\* /disk/space/mek11/GOESdatanew (the first of the globir lines is the one that was just changed). Given the second globir line in the 'redirect.k LIST' listing, the following must have been run at one point: redirect.k ADD globir.\\* \"/disk/space/mek11/USdata/GOES -- OR -- REDIRECT ADD globir.\* "/disk/space/mek11/GOESdatanew When running a McIDAS command from the Text and Command window in a session, you do not have to escape the '*'. This only has to be done on the Unix command line since the Unix shell (the C shell in your case) will interpret the '*' unless it is escaped. So, I removed the errant REDIRECTion using: redirect.k DEL globir.\\\* (the extra '\' is needed since the first '\' escapes the second and the third escapes the '*'). Your set of REDIRECTions is now what you want: redirect.k LIST Number of active redirection entries=1 globir.* /disk/space/mek11/USdata/GOES redirect.k: Done and you can see all of the files you copied to /disk/space/mek11/USdata/GOES: dmap.k globir PERM SIZE LAST CHANGED FILENAME DIRECTORY ---- --------- ------------ ----------------- --------- -rw- 3737128 Jun 10 14:14 globir.02183.0015 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0045 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0115 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0145 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0215 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0245 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0315 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0345 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0415 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0445 /disk/space/mek11/USdata/GOES -rw- 3737128 Jun 10 14:14 globir.02183.0515 /disk/space/mek11/USdata/GOES ... >(2) When the above works, I am planning to do this: >Lwu POKE globir.02183.0015 >Lwu POKE globir.02183.0030 >. >. >. >BATCH MYDATA.BAT Running this BATCH command only has to be done once! I see from your setup that it has already been done, so you do not need to execute it again. >IMGCOPY IR183/AREA.1 IR183/IMAGES.3000 LATLON=39 100 SIZE=200 400 >AXFORM 3000 out183 FTYPE=ASC NAV=YES TYPE=TEMP OK. Remember that you will use 'lwu.k' from the Unix command line and LWU from the McIDAS Text and Command Window. >QUESTION: Could I do the above to process the above 48 files. Can this step >create 48 output files,...? In short, my question is what is the best way to >get 48 output files corresponding to the 48 datafiles? I would run the lwu.k POKE commands once on the input images and then put the sectorization (IMGCOPY) and dump (AXFORM) into a loop in either a Unix shell script (where the entire process would be run outside of a McIDAS session) or in a McIDAS BATCH or McBASI script. If you are adept at Unix shell scripting, I would recommend going that route. If you are not, and if you plan on using McIDAS routinely, I would recommend learning a bit about McIDAS BATCH and McBASI scripts. BATCH is a very simple MSDOS 'batch' like processor. You can put multiple commands in an ASCII text file and then execute them in one go using the BATCH (batch.k) command in McIDAS. McBASI is a basic like interpreter that supports looping constructs through a 'goto' command. When writing your script, please remember that the name of the output files need to be unique so that you don't continually overwrite the same file: axform.k 3000 out183 FTYPE=ASC NAV=YES TYPE=TEMP ^_ base name of output files needs to change for each loop iteration >I apologize for my seemingly endless questions, but we are almost at the >final stage so bear with me. 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.