Define the newline string:
newline = string(10B)
Then incorporate it into the text:
myTwoLineString = ‘First Line’ + newline + ‘Second Line’
From: https://www.nv5geospatialsoftware.com/Support/Forums/aft/1281, entitled:
Character escapes for strings in IDL (carriage returns, etc)
Note that IDL 2-dimensional arrays are given as Z[A,B] where A is column ref; B is row ref
x[*] means take each element of x (separately), so
x[*] = y[*] means,
x[0] = y[0], x[1] = y[1], … up to all elements of the arrays
x[0:2] is essentially does the same but on a subset of an array; eg
take elements 0 through 2 of the array (and do “whatever”)
I read also that this notation, esp on lhs, is much much faster than
conventional looping etc.
IDL> print, file_which(‘chjuldaytolmstGALFA.pro’)
/usr/share/astro/idlshare/locallib/chjuldaytolmstGALFA.pro
and more specifically:
from https://stackoverflow.com/questions/29986130/idl-procedure-wont-compile
But when I try to find the procedure using “Findpro” I get
Procedure CHLOADCT found in directory /data/clh93/colortables/CH/
So my paths are right. I don’t understand why it won’t find my procedure, does anyone know what’s going on?
Answers:
Things to check in situations like this:
.pro extension; the case of the filename and routine call must match or the filename must be all lowercase (just use all lowercase in filenames!)my_routine.pro is in your !path:
IDL> print, file_which('my_routine.pro')
It will return an empty string if it can’t find it.
!path twice and you are getting someone else’s or an old versionFortran has the ability to send one somewhere upon an I/O error:
read(43,100,end=50) x,y,z in which case program will go to statement labeled “50′ upon a read error.
IDL does not have such a simple way to do it. But after many hours, I got an equivalent process to work. An example is in the
/data/psrdata/rmgalprojs/rm2016/AO_Pulsars_RM/Longi_RM_Plots.pro file, specifically in
the PersArmNoIntArm data input section.
——————————————————————————
The same section of code illustrates painful read in of a complicated data file, where a single (long) row had been turned into six. It is similar to but not quite identical to fortran. I had to eliminate all format = ‘(sd;jkfsd;jkg)’ statements because idl and i (≡fortran) did not interpret them the same. Instead I had to force variables to have the right type before reading data into them, by initializing them. For example, to read the following variables properly, i did things like:
ztext = ‘ ‘
xfloat = 3.5
ydoubleprecision=8.d0
Then when I read a file into those variables from a file , idl will treat those variables as the types given in the initialization statements.
some idl commands look exactly like their unix systers, while others are idl knockoffs and therefore require idl syntax
cd ,’/data/psrdata’
pwd
$ls -als | grep sav (the dollar tells idl that the following is a unix command)
To create IDL multiple line graphics captions, insert a !C inside string at desired location.
( !C means “carriage return” )
canny has idl 8.6.1
mirzy has idl 8.7 (I think)
as noted in prev post, using canny on gal mag fld proj with idl for first time in years, i hit a bug that was 8.6.1 related (which is why i hadn’t had this problem on mirzy!)
Because mirzam was down tonight I used idl on canopus instead. In trying to run some idl galactic magnetic field idl programs on canopus, I kept hitting an obscure error on coyote’s cggreek routine which makes greek letters for plots. Googling it I found that an idl 8.6.1 (as on canny) error prevented old cggreek from working. (It worked ok forever on mirzy, which has I think idl 8.7)
So I installed the new cggreek from github to thuban2’s /var/share/astro/idleshare/coyote. but this didn’t work! why? because i had to install it onto /var/share/astro_centos7/idleshare/coyote Note because of access issues, one can not install directly onto /usr/share/astro on mirzy or canny, but must instead go to thuban2/var/share/astro_centos7/ as above (and see below).
by the way i used su cp etc etc on thuban 2 to overcome permission issues on canny or mirzy themselves, but prev post shows that su – on thuban2 might be easier
in idlde, go to window>>preferences>>General>>Editors>>text editors and place a checkmark on “show line numbers” and then go to bottom and apply and save
very hard to find this –googling and manuals did not help –joel
Solution from:
https://stackoverflow.com/questions/25167780/output-2-array-values-to-a-text-file-using-idl
IDL> x = findgen(10)
IDL> y = findgen(10) * 2
IDL> print, transpose([[x], [y]]), format='(2F)'
--Joel