To get this right:
Split takes column 2, splits the string at the x's and saves its output in an array(like) variable for later usage.
Sadly, pixels get calculated to 0 but the bold text is working, thank you.
I'm now stuck at further parsing of bitrates, i'd like to put a 'kb' at its end as long bitrates do not exceed 1mb, then 'mb' should be appended.
Hi,
My file has 2 fields and millions of lines.
variableStep chrom=Uextra span=25
201 0.5952
226 0.330693
251 0.121004
276 0.0736858
301 0.0646982
326 0.0736858
401 0.2952
426 0.230693
451 0.221004
476 0.2736858
Each field either has a... (6 Replies)
I am trying to do some math, so that I can compare the average of six numbers to a variable.
Here is what it looks like (note that when I divide really big numbers, it isn't a real number):
$ tail -n 6 named.stats | awk -F\, '{print$1}'
1141804
1140566
1139429
1134210
1084682
895045... (3 Replies)
hi I want to write a script, while using the SED editor, to output the text, in this case a variable, to the result file but highlighted it in bold, is it possible to do that? can you tell me how?
eg. in text.txt
sed '$ a\
'$variable'
' <text.txt >text2.txt
so it will add the... (2 Replies)
Hi I have this list
592;1;Z:\WB\DOCS;/FS3_100G/FILER112/BU/MPS/DOCS;;;;\\FILER112\BUMPS-DOCS\;580,116,544,878 Bytes;656,561 ;77,560
592;2;Z:\WB\FOCUS;/FS3_100G/FILER112/BU/MPS/FOCUS;;;;\\FILER112\BUMPS-FOCUS\;172,430 Bytes;6 ;0 ... (12 Replies)
Based on input
ail,UTT,id1_0,COMBO,21,24,21,19,85
al,UTHAST,id1_0,COMBO,342,390,361,361,1454
and awk code as
awk -F, '{ K=0; for(i=NF; i>=(NF-4); i--) { K=K+$i; J=J+$i;} { print K } } END { for ( l in J ) printf("%s ",J); }'
I'm trying to add columns and lines in single line. line... (6 Replies)
Hi
main object is categorize the difference of data-values (TLUFT02B - TLUFT12B).
herefor i read out data-files which are named
acording to the timeformat yyyymmddhhmm.
WR030B 266.48 Grad 0
WR050B 271.46 Grad 0
WR120B 268.11 Grad 0
WV030B 2.51 m/s ... (6 Replies)
Hi expert,
I have log :
TOTAL-TIME : 2125264636
DATA-BYTES-DOWN : 3766111307032
DATA-BYTES-UP : 455032157567
DL = (3766111307032/2125264636)/1024 = 1.73
UL = (455032157567/2125264636)/1024 = 0.21
I want the result :
TOTAL = 1.94 ... (4 Replies)
FYI,
I'm slowly removing a lot of the bold font-styles from titles of discussions, forum titles, etc
I'm not removing bold for the entire site because we do need bold from time to time, especially in posts and sometimes in other places.
However, the original forum style had way too much... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT SUSE
funsky
funsky(1) SAORD Documentation funsky(1)NAME
funsky - convert between image and sky coordinates
SYNOPSIS
funsky iname[ext] # RA,Dec (deg) or image pix from stdin
funsky iname[ext] [lname] # RA, Dec (deg) or image pix from list
funsky iname[ext] [col1] [col2] # named cols:units from stdin
funsky iname[ext] [lname] [col1] [col2] # named cols:units from list
OPTIONS -d # always use integer tlmin conversion (as ds9 does)
-r # convert x,y to RA,Dec (default: convert RA,Dec to x,y)
-o # include offset from the nominal target position (in arcsec)
-v # display input values also (default: display output only)
-T # output display in rdb format (w/header,tab delimiters)
DESCRIPTION
Funsky converts input sky coordinates (RA, Dec) to image coordinates (or vice versa) using the WCS information contained in the specified
FITS file. Several calling sequences are supported in order to make it easy to specify coordinate positions in different ways.
The first required argument is always the input FITS file (or extension) containing the WCS information in an extension header. Note that
the data from this file is not used. By default, the program converts input RA and Dec values to X and Y using this WCS information. If the
WCS is associated with a FITS image, then the X,Y values are image values. If the WCS is associated with a binary table, then the X, Y val-
ues are physical values. To convert X,Y to RA and Dec, use the -r (reverse) switch.
If no other command arguments are supplied, then the input positions are read from the standard input. Each line is assumed to contain a
single coordinate position consisting of an RA in hours (or X in pixels) followed by a Dec in degrees (or Y in pixels). The usual delim-
iters are supported (spaces, commas, tabs). For example:
# read from stdin, default column names and units
[sh] funsky snr.ev
22.982695 58.606523 # input RA (hrs), Dec(deg)
510.00 510.00
22.982127 58.607634 # input
512.00 510.50
22.981700 58.614301 # input
513.50 513.50
^D # end of input
If a second argument is supplied, this argument is assumed to be a file containing RA (X) and Dec (Y) positions. The file can either be an
ASCII table or a FITS binary table. The order of columns is unimportant, if the table has a column header. In this case, the names of the
columns must be one of "RA", "DEC", or "X", "Y" for sky to image and image to sky conversions, respectively. If the table has no header,
then once again, RA (X) is assumed to first, followed by DEC (Y). For example:
# read from file, default column names and units
[sh] cat hd.in
RA DEC
------------------
22.982695 58.606523
22.982127 58.607634
22.981700 58.614301
[sh] funsky snr.ev hd.in
510.00 510.00
512.00 510.50
513.50 513.50
If three arguments are supplied, then the input positions again are read from the standard input. Each line is assumed to contain a single
coordinate position consisting of an RA (or X in pixels) followed by a Dec (or Y in pixels), with the usual delimiters supported. However,
the second and third arguments now specify the column names and/or sky units using a colon-delimited syntax:
[colname]:[h|d|r]
If the colname is omitted, the names default to "RA", "DEC", "X", "Y", "COL1", or "COL2" as above. If the units are omitted, the default is
hours for RA and degrees for Dec. When the -r switch is used (convert from image to sky) the units are applied to the output instead of
the input. The following examples will serve to illustrate the options:
# read from stdin, specifying column names (def. units: hours, degrees)
[sh] cat hd.in
MYRA MYDEC
------------------
22.982695 58.606523
22.982127 58.607634
22.981700 58.614301
[sh] funsky snr.ev MYRA MYDEC < hd.in
510.00 510.00
512.00 510.50
513.50 513.50
# read from stdin, specifying column names and units
[sh] cat dd.in
MYRA MYDEC
------------------
344.740432 58.606523
344.731900 58.607634
344.725500 58.614301
[sh] funsky snr.ev MYRA:d MYDEC:d < dd.in
510.00 510.00
512.00 510.50
513.50 513.50
# read stdin, convert image to sky, specifying output sky units
[sh] cat im.in
510.00 510.00
512.00 510.50
513.50 513.50
[sh] cat im.in | funsky -r snr.ev :d :d
344.740432 58.606523
344.731900 58.607634
344.725500 58.614301
Finally, four command arguments specify both and input file and column names and/or units:
[sh] cat dd.in
MYRA MYDEC
------------------
344.740432 58.606523
344.731900 58.607634
344.725500 58.614301
[sh] funsky snr.ev dd.in MYRA:d MYDEC:d
510.00 510.00
512.00 510.50
513.50 513.50
# read file, convert image to sky, specifying output sky units
[sh] cat im.in
510.00 510.00
512.00 510.50
513.50 513.50
[sh] funsky -r snr.ev im.in :d :d
344.740432 58.606523
344.731900 58.607634
344.725500 58.614301
By default, the output of funsky consists only of the converted coordinate position(s), one per output line. This makes parsing in shell
scripts easy. Use the -v (verbose) switch to specify that the input coordinates should be pre-pended to each line. For example:
[sh] cat dd.in
MYRA MYDEC
------------------
344.740432 58.606523
344.731900 58.607634
344.725500 58.614301
[sh] funsky snr.ev dd.in MYRA:d MYDEC:d
510.00 510.00
512.00 510.50
513.50 513.50
[sh] funsky -v snr.ev dd.in MYRA:d MYDEC:d
344.740432 58.606523 510.00 510.00
344.731900 58.607634 512.00 510.50
344.725500 58.614301 513.50 513.50
In addition, a full starbase table can be output using the -T (table) switch. This switch can be used with or without the -v switch. If
the -T and -v are both specified, then a descriptive header parameters are output before the table (mainly to remind you of the sky
units):
# output table in non-verbose mode
[sh] funsky -T snr.ev dd.in MYRA:d MYDEC:d
X Y
------------------------
510.00 510.00
512.00 510.50
513.50 513.50
# output table in verbose mode
[sh] funsky -T -v snr.ev dd.in MYRA:d MYDEC:d
# IFILE = /Users/eric/data/snr.ev
# ICOL1 = MYRA
# ICOL2 = MYDEC
# IUNITS1 = d
# IUNITS2 = d
# OCOL1 = X
# OCOL2 = Y
MYRA MYDEC X Y
------------------------------------------------
344.740432 58.606523 510.00 510.00
344.731900 58.607634 512.00 510.50
344.725500 58.614301 513.50 513.50
Finally, the -d (ds9) switch mimicks ds9's use of integer TLMIN and TLMAX values for all coordinate transformations. FITS conventions
seem to call for use of floating point TLMIN and TLMAX when the data are floats. This convention is followed by funsky but results in a
small discrepancy with ds9's converted values for floating point data. We will remedy this conflict in the future, maybe.
SEE ALSO
See funtools(7) for a list of Funtools help pages
version 1.4.2 January 2, 2008 funsky(1)
02-12-2015
but the bold text is working, thank you. 