Machine% cp ~plewis/public_html/teaching/unix/shellCode/envi2gif. Machine% cp ~plewis/public_html/teaching/unix/shellCode/doit.pro. You can run this script from the command line: run localMaximum), decoding some environment variables (WS = long(getenv('IDL_SIZE')) etc.), running one or more procedures, and exiting.
#Idl size code
sav file (pre-compile)Īny interface code you write is likely to follow the same form - setting up the envi/idl environment (envi, /restore_base_save_files envi_batch_init, log_file=LOGFILE. it might be more efficient to store this as a. Print, 'operating on ',inimage,' to ',outimage,' with window ',WS now get some other unix environment variables now compile the idl code in localMaximum.pro now we initiate the envi batch file processing This next line sets the IDL variable 'LOGFILE' to the value of the unix environment variable 'IDL_LOGFILE' this next line of code is something you always need The next piece of code we need to look at is doit.pro, another piece of idl code that we are using as an interface between information from the csh program and a call to the procedure localMaximum. This local maximum is taken over a window of -WS to WS (i.e. The filtering operation is a local maximum (as the name implies). This idl procedure reads in an envi format image (via the variable inimage) and filters the image to write out an (envi format) image (variable outimage). We will be going through that code in a later session, but for now, just note that it contains an idl procedure ('pro') called localMaximum (defined in the file as 'pro localMaximum, inimage, outimage, WS=WS'). Lets start by looking at the envi/idl code localMaximum.pro. In this session, we will build a unix csh program that will loop around an envi/idl program. rw- 1 root other 2023424 May 11 15:05 objectClass.An example csh interface to an envi batch file (with potential for parallel processing) rw- 1 root other 151719936 May 11 15:05 msgRecipientAddress.bdb rw- 1 root other 2236416 May 11 15:05 msgEventDescriptor.bdb * limiting factors: sizeof(ID), thread stack size * IDL sizes - likely should be even bigger Also with the current size of my DB (id2entry ~ 5Gig) does the default really cover my specific case now or am I encountering performance degradation without realizing it?
#Idl size how to
From: "Mcclure, James (James)** CTR **" Ĭan anyone enlighten me on guidelines to IDL sizing and how to determine the number of items in a particular index file? I found the defaulted values in idl.h associated with a Berkeley DB backend, but I am not sure what those values really mean (per index or total?).
0 kommentar(er)
