Jump to content
PDS Geosciences Node Community

Susie Slavney

Geo Staff
  • Posts

    215
  • Joined

  • Last visited

Posts posted by Susie Slavney

  1. Sandy,

    Here is the response from Paul Geissler at the PDS Imaging Node.

     

    "The Galileo images have to be corrected for camera pointing uncertainty.

    There is exact knowledge of where the target was and where the spacecraft was, but just an estimate of where the camera was pointed. There are tools to do this in ISIS2 (limbfit in qview allows the user to pick points along the limb and fit a circle to them, and writes updated camera angles to the image label; see also the ISIS2 program deltck). These software systems are also useful for radiometric calibration (ssical in ISIS2, for example).

     

    Documentation describing ISIS2 processing of Galileo images:

    http://isis.astrogeology.usgs.gov/Isis2/isis-bin/voyager_mosaic.cgi

     

     

    Download ISIS2 software:  http://isis.astrogeology.usgs.gov/."

     

    I hope this information helps you.

     

    Susie Slavney

    PDS Geosciences Node

  2. I'm not familiar with Galileo data but I'll try to find someone at the PDS Imaging Node to help you. Meanwhile, here are some suggestions. There are several Galileo SSI image data sets at the PDS Imaging Node. I don't know which one you are using, but if you can find your way back to the place where you downloaded it, look in the top-level directory of that data set and read the files AAREADME.TXT and ERRATA.TXT to see if they give any clues about the correct way to view the images. I assume you have already looked in the label file (.LBL) that accompanies each image. The main documentation is the file REDRSIS.PDF in the DOCUMENT directory.

     

    Susie Slavney

    PDS Geosciences Node

  3. The SHARAD data in the file you mentioned are stored as a binary table, not ASCII. The format is described in the PDS label file, here:

    http://pds-geosciences.wustl.edu/mro/mro-m-sharad-4-rdr-v1/mrosh_1002/data/rdr25xxx/rdr2501901/r_2501901_001_ss19_700_a.lbl

    and in the format file http://pds-geosciences.wustl.edu/mro/mro-m-sharad-4-rdr-v1/mrosh_1002/label/rdr.fmt. It is also described in the SHARAD Reduced Data Record Software Interface Specification (http://pds-geosciences.wustl.edu/mro/mro-m-sharad-4-rdr-v1/mrosh_1002/document/rdrsis.pdf). In particular, see section 4.2, Data Product Overview, and section 5.1, Data Product Structure and Organization.

     

    In answer to the question about surface clutter, section 4.2 warns that the data "may contain artifacts due to off-nadir surface reflections, the so-called clutter...". So no, the clutter has not been removed from the data file.The JPEG browse image for this data file is here:

    http://pds-geosciences.wustl.edu/mro/mro-m-sharad-4-rdr-v1/mrosh_1002/browse/rdr25xxx/rdr2501901/r_2501901_001_ss19_700_a_b.jpg.

    The label file in the same directory explains how the data were processed to create the JPEG image:

    http://pds-geosciences.wustl.edu/mro/mro-m-sharad-4-rdr-v1/mrosh_1002/browse/rdr25xxx/rdr2501901/r_2501901_001_ss19_700_a_b.lbl

     

    There are no MARSIS Reduced Data Records for orbit 2682 in PDS. Reduced data only through orbit 2418 have been delivered by the MARSIS team to PDS.There are some raw data products for this orbit in http://pds-geosciences.wustl.edu/mex/mex-m-marsis-2-edr-ext1-v1/mexmde_1002/data/edr268x/.

  4. I have a little more information for you about the handful of high temperature values in the file

    http://pds-geosciences.wustl.edu/viking/vl1_vl2-m-lr-2-edr-v1/vl_9010/data/vl1c1ht.tab.

    This is from the scientist who prepared this data set for PDS from the paper archive.

     

    "The values were correctly transcribed from the paper copy of the data. The first high value is an unexplained anomalous measurement and is tagged as such in the data file (see the last column). There is also a note in the ERRATA.TXT file about these types of anomalous values.

    The high temperatures at the end of the file are from heating the chamber to close out the measurement cycle, according to the hand-written notes on the paper copies of the data. The heating was done to dry the sample before purging gases from the chamber and is briefly mentioned in the VOLINFO.TXT file."

     

    The files mentioned, ERRATA.TXT and VOLINFO.TXT, may be found here:

    http://pds-geosciences.wustl.edu/viking/vl1_vl2-m-lr-2-edr-v1/vl_9010/errata.txt

    http://pds-geosciences.wustl.edu/viking/vl1_vl2-m-lr-2-edr-v1/vl_9010/document/volinfo.txt

  5. Dear Aidan,

    To answer your questions:

     

    a) What kind of nutrient solution was used?

     

    Please see the document Carbon 14 Labeled Organic Substrates, online at

    http://pds-geosciences.wustl.edu/viking/vl1_vl2-m-lr-2-edr-v1/vl_9010/extras/substrat.htm.

     

    B) What device was used to measure the temperature?

     

    An overview and schematic drawing is in the Labeled Release Instrument description here:

    http://pds-geosciences.wustl.edu/viking/vl1_vl2-m-lr-2-edr-v1/vl_9010/extras/lridesc.htm

    This document includes references to publications that explain the experiment in greater detail.

     

    Additional information is available on the Viking Lander Labeled Release Experimenter's Notebook page:

    http://pds-geosciences.wustl.edu/viking/vl1_vl2-m-lr-2-edr-v1/vl_9010/extras/index.htm.

     

    Regards,

    Susie Slavney

     

  6. A user emailed this question to the Geosciences Node:

    "Dear LOLA Team,

    I was not sure but I probably found a large mount of data gap when processing LOLA-GDR data. The attached file [not included here] with resolution of 1024pixels/degree is a good representative for lacking data between adjacent orbital LOLA data. This part of a projected map is established through a combination of a set of LOLA-GRD data using GMT software. Easily seen from this map, some area can display more detailed information than others lacking altimeter data in adjacent orbits which is relative flat. If you size it up, you can see it more clearly. Is it necessary that if i need to build higher resolution images, i should process RDR or EDR data? Could you please give me some suggestion? Thanks."
     
    The LOLA Team answers:
    "The LDEM_1024/degree is very sparse at midlatitudes. This GDR is nearly 3 years out of date,  since just after the end of the Science Mission month 5 (Jan 31, 2011 I think).
     
    The LOLA ground track spacing still has gaps of several km in places, in spite of 20,000+ orbits.
    The LDEM_512 is a better dataset with less gaps and is up to date.
    Much of the improvement in these data is due to continued refinement of orbit solutions, including laser ranging,
    and the use of high-degree GRAIL gravity.
     
    At some point this year we plan to redo 1024 with the "ultimate" dataset, which to generate is very compute intensive.
     
    The complete terrain information is available from the full RDR dataset - I still use the SOFTWARE tool
    'rdr2table LOLARDR.DAT A H M Lregion.prm'
     to build a point cloud for any particular region - it is fast - also the PDS website has
    software that extracts the individual data points, Any detector, Header line, Manual edits included, Limited to lon -lat region.prm."
     
     
  7. Yes, I believe it includes ENVRDR3 data, but I'm guessing because I see the format file ENVRDR3.FMT in the LABEL directory. I'm no REMS expert. If you have trouble finding what you need, please ask the PDS Atmospheres Node contact for REMS, Lyle Huber (lhuber@nmsu.edu).

  8. Dear Ranjan,

    The SHARAD data are not image files. They are indeed columns of binary numbers. To analyze the data you will need to understand the contents of the files. Here are some places to look, if you haven't looked there already.

     

    The primary documentation for the SHARAD data is the Data Product Specification (http://pds-geosciences.wustl.edu/mro/mro-m-sharad-4-rdr-v1/mrosh_1002/document/rdrsis.pdf).

     

    Each SHARAD data file is accompanied by a PDS label in a separate file with the same name, extension .LBL. The label has information about the size and format of the records in the file, along with metadata about how and when the data were acquired. The PDS labels refer to another label file that describes the columns in detail: http://pds-geosciences.wustl.edu/mro/mro-m-sharad-4-rdr-v1/mrosh_1002/label/rdr.fmt.

     

    The JPEG images in the browse directory are created here at the Geosciences Node. The PDS labels for the JPEG images include a description of the algorithm used to read the SHARAD data.

     

    And finally, with the permission of the authors, I have posted the IDL scripts that implement this algorithm to create the JPEGs. You may find it useful as a model for reading the data files. See our SHARAD web page, under Tools (http://pds-geosciences.wustl.edu/missions/mro/sharad.htm).

     

    Regards,

    Susie Slavney

     

  9. Agnes,

    First of all, were you unable to find enough information in the documentation? Try looking at these files:

    1. the tracking data description in http://pds-geosciences.wustl.edu/lro/lro-l-rss-1-tracking-v1/lrors_0001/document/lro_desc_trk.txt

    2. the description of the columns in the binary table in http://pds-geosciences.wustl.edu/lro/lro-l-rss-1-tracking-v1/lrors_0001/label/lro_trk.fmt

    3. the archive Software Interface Specification document in http://pds-geosciences.wustl.edu/lro/lro-l-rss-1-tracking-v1/lrors_0001/document/lrors_arch_sis.pdf

     

    If this doesn't help, let me know and I'll see if I can find someone who can answer your questions.

     

    Susie Slavney

    PDS Geosciences Node

     

  10. I think you are referring to the LOLA GDR data set, LRO-L-LOLA-4-GDR-V1.0, http://pds-geosciences.wustl.edu/missions/lro/lola.htm, right? I am not sure whether you are asking how to get the elevation values or the latitude and longitude location. Either way, look in the label file that accompanies a given image, for example http://pds-geosciences.wustl.edu/lro/lro-l-lola-3-rdr-v1/lrolol_1xxx/data/lola_gdr/cylindrical/img/ldem_16.lbl.

     

    To find the elevation in meters for a given pixel, multiply the pixel value by the SCALING_FACTOR and add the OFFSET. In the example label, SCALING_FACTOR is 0.5 and OFFSET is 1737400.

     

    To get the latitude and longitude corresponding to a given pixel, you'll need the values for CENTER_LONGITUDE, CENTER_LATITUDE, SAMPLE_PROJECTION_OFFSET, LINE_PROJECTION_OFFSET, and RES (MAP_RESOLUTION), all of which are found in the label file.  Then plug these values into the map projection equations in the file DSMAP.CAT (http://pds-geosciences.wustl.edu/lro/lro-l-lola-3-rdr-v1/lrolol_1xxx/catalog/dsmap.cat) for simple cylindrical projections or DSMAP_POLAR.CAT (in the same folder) for polar stereographic projections.

  11. The LOLA RDR data set has the latitude, longitude, and radius values for each LOLA measurement. The RDR data are stored as binary tables in the format described by this file:

    http://imbrium.mit.edu/LABEL/LOLARDR.FMT

     

    The data are organized in time order in subdirectories by mission phase, here:

    http://imbrium.mit.edu/DATA/LOLA_RDR/

     

    Please read the LOLA RDR SIS (http://pds-geosciences.wustl.edu/lro/lro-l-lola-3-rdr-v1/lrolol_1xxx/document/rdrsis.pdf) for a complete description of the instrument's operation and the RDR data product.

     

    Susie Slavney

×
×
  • Create New...