[X] My Assistant

[JohnVV]

read through and run the examples in the Workshop
https://isis.astrogeology.usgs.gov/IsisWork...hp/IsisWorkshop

isis3 can be a bit daunting .
First the linux requirement ( there is a mac port)
the rhel 6 build runs just fine on ( i have tested )
CentOS 6.8
ScientificLinux 6.7 ( will be 6.8 soon )
Opensuse 13.2 and 42.1
-- WARNING on Fedora - has issues

Then the old Voyager data

Those that have been fallowing any of the reprocessing threads have seen the images
missing lines and reseaus marks and it is 8 bit

and searching for data can be a problem
unless you are just garbing it all

for this post i am using a few Blue,Green and Orange ( no red filter) ( orange and blue make red )
and using the pds atlas
http://pds-imaging.jpl.nasa.gov/search/
-- WARNING!!!!!!
this archive sends isis3 incompatible "img" files !!!
the wget script needs to be "CORRECTED!!!

for example the "atlas_wget_script" give this

CODE

wget -O c1113006.img 'http://pds-imaging.jpl.nasa.gov/pds/prod?q=OFSN+%3D+/data/voyager//vg_0010/extras/pds/neptune/c1113xxx//c1113006.img+AND+RT+%3D+RAW'
wget -O c1113017.img 'http://pds-imaging.jpl.nasa.gov/pds/prod?q=OFSN+%3D+/data/voyager//vg_0010/extras/pds/neptune/c1113xxx//c1113017.img+AND+RT+%3D+RAW'
wget -O c1113039.img 'http://pds-imaging.jpl.nasa.gov/pds/prod?q=OFSN+%3D+/data/voyager//vg_0010/extras/pds/neptune/c1113xxx//c1113039.img+AND+RT+%3D+RAW'

these img files can not be opened with "voy2isis"
You need the imq ( Q on the end )
a simple edit of the script will solve this

--fixed--

CODE

wget -O c1113006.imq 'http://pdsimage.wr.usgs.gov/archive/vg1_vg2-n-iss-2-edr-v1.0/vg_0010/neptune/c1113xxx/c1113006.imq'
wget -O c1113017.imq 'http://pdsimage.wr.usgs.gov/archive/vg1_vg2-n-iss-2-edr-v1.0/vg_0010/neptune/c1113xxx/c1113017.imq'
wget -O c1113039.imq 'http://pdsimage.wr.usgs.gov/archive/vg1_vg2-n-iss-2-edr-v1.0/vg_0010/neptune/c1113xxx/c1113039.imq'

the voyager " *.imq " files are gziped compressed archives

isis3 has BUILT IN batch support -- very handy

to ingest into isis3 and also get a "preview" image i use this script

CODE

#!/bin/sh
ls *.imq | sed s/.imq// > cube.lis
voy2isis from=\$1.imq to=\$1.cub -batchlist=cube.lis
spiceinit from=\$1.cub -batchlist=cube.lis
voycal from=\$1.cub to=\$1.cal.cub -batchlist=cube.lis
isis2std from=\$1.cal.cub to=\$1.png minpercent=0.1 maxpercent=99.9 -batchlist=cube.lis

i have now a calibrated and geo-referenced image
these images


and they need work ( the pointing data is OFF - hay this is from Voyager after all )


( preview of "c1113006" using isis3's "Grid " program )


i will worry about that later

the spiceinit'ed and voycal images are now 2.5 Meg 32bit float images -- "c1113006.cal.cub"
have a look in Qview

CODE

qview c1113006.cal.cub

-- if you are going to use the built in isis3 tools then leave the NULL pixels and do not run stretch

-- for using gimp or other tools

the missing lines are "NULL" data ( px value -3.8 E^38 )
and some low instrument values that are negative pixel values
-- for cleaning up and exporting the images to Gimp2.9.3 ( or Krita )these need to be zero

a handy isis3 tool is "stretch "

CODE

stretch from=c1113006.cal.cub to=c1113006.cal1.cub null=0.0 lis=0.0

on to exporting it to a RAW image so it can be cleaned up and then moved back into isis3
best done in a new sub folder

CODE

cubeatt from=c1113006.cal1.cub to=c1113006.cal1.raw+BSQ+detached

you now have a raw and detached headers
( rename c1113006.cal1.raw.cub to c1113006.cal1.raw )

[Brian Burns]

So here are some steps to make a mosaic map (might be better ways to do this) -

First download some IMQ files, e.g. from http://pds-rings.seti.org/vol/VG_0xxx/VG_0...PITER/C1620XXX/

# convert the IMQ files into ISIS image cubes
$ voy2isis from=C1620000.imq to=im00.cub
$ voy2isis from=C1620004.imq to=im04.cub
$ voy2isis from=C1620008.imq to=im08.cub
$ voy2isis from=C1620012.imq to=im12.cub
$ voy2isis from=C1620016.imq to=im16.cub
$ voy2isis from=C1620020.imq to=im20.cub

# attach SPICE position and pointing information to each cube, from the web
$ spiceinit from=im00.cub web=yes
$ spiceinit from=im04.cub web=yes
$ spiceinit from=im08.cub web=yes
$ spiceinit from=im12.cub web=yes
$ spiceinit from=im16.cub web=yes
$ spiceinit from=im20.cub web=yes

# initialize a mapping file
$ maptemplate map=map.txt projection=SimpleCylindrical clon=0.0

# project the first image cube to a simple cylindrical map, and save the updated mapping file
$ cam2map from=im00.cub to=map00.cub map=map.txt > map.txt

# project remaining image cubes to simple cylindrical maps using the same parameters
$ cam2map from=im04.cub to=map04.cub map=map.txt pixres=map
$ cam2map from=im08.cub to=map08.cub map=map.txt pixres=map
$ cam2map from=im12.cub to=map12.cub map=map.txt pixres=map
$ cam2map from=im16.cub to=map16.cub map=map.txt pixres=map
$ cam2map from=im20.cub to=map20.cub map=map.txt pixres=map

# now combine all the maps into a single mosaic map
$ ls -1 map??.cub > map.lis
$ automos fromlist=map.lis mosaic=mos.cub

# view the mosaic
$ qview mos.cub

# convert it to a jpeg (3.5MB)
$ isis2std from=mos.cub to=mos.jpg format=jpeg



There are better ways to combine the maps so the seams don't show so much, using averaging, or the program noseam, but I haven't tried those yet. And there are pointing errors, of course...

There's a program jigsaw, which seems like it might help with correcting pointing information, given correspondences between images (which can be calculated using findfeatures)-

findfeatures applies feature-based matching (FBM) algorihms using the full suite of OpenCV feature matching frameworks. The points detected by these algorithms are associated with special surface features identified by the type of detector algorithm designed to identify certain charcteristics.
https://isis.astrogeology.usgs.gov/Applicat...ndfeatures.html

jigsaw performs a bundle adjustment on a group of overlapping Isis 3, level 1, cubes from framing and/or line-scan cameras. The adjustment simultaneously refines the selected image geometry information (camera pointing, spacecraft position) and control point coordinates (x,y,z or lat,lon,radius) to reduce boundary mismatches in mosaics of the images.
https://isis.astrogeology.usgs.gov/Applicat...saw/jigsaw.html

Will eventually try these out also.

One problem is that cam2map is very slow - it takes about a minute on my laptop to do a simple cylindrical projection, though I'm using a virtual machine so I'm not sure how much of that is overhead. Hopefully there will be a way to speed this up.