Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Existing parameters are in italics in first column

New parameters / ideas from workshop in dark red-brown

Usage in PDS_speclib service no longer consistent with column 3 are underlined in blue (would have to be changed also in the 2 DLR services)


Lab spectroscopy extension

 group related to:

Iterated from SSHADE and other proposals in Rome

 Initial proposal from PDS_speclib implementation

Existing parameters in italics

 

 

No longer consistent with workshop outcomes

New from workshop

group related to:

 

 

 

 

 

 

target_class

sample reference

'sample', constant

'sample', constant

target_name

 

Provides name of a meteorite, lunar sample, IDP, micrometeorite, etc from which the sample is extracted

 provides an ID of the sample

 

 

- empty otherwise, no local ID

Introduces the name of a meteorite or lunar sample when applicable.

alt_target_name

 

has to be related to target_name only - can't be used to store extra info on sample identification

 

sample_id

 

will provide name/ID of measured sample in local collection

 Various parts of the same sample can be indicated and described in sample_desc (such as "Location A", etc)

 

 

 

 

producer_name

measurement origin

These two provide enough credits in the table (agreed)

 provide reference to whom measured the sample

producer_institute

 

 

 

instrument_host_name

 

Standard name of the lab/facility

Standard name of the lab/facility

instrument_name

 

Name of instrument (as in publications)

 Name of instrument (as in publications)

 

 

 

 

sample_classification

sample description

provides composition as group, class, sub-class, etc… of sample, concatenated in a hash-list (=> flexible searches with LIKE and %)

 

 

 

Name of mineral to be included

 

 

 

Should include specification "meteorite" plus the meteorite type when applicable, as well as description of (main) mixtures ingredients

 

 

 

Meteorite types as in Krot et al 2005. Dana or Struntz classification tags can be used for minerals.

 

 

 

Minor/trace components are not welcome here (would multiply false alarms)

 

grain_size_min

 

Min/max defined somehow, left to data provider

 provide the particle size range in µm

grain_size_max

 

(not expected to be intensively used) - code for bulk ?

 A very large value (eg, >1000 µm) can be used locally in a service to identify bulk material

 

 

 

- see if we define a code for this (-1 could do, but we also have to reserve a code for N/A

? Sample_origin ?

 

Need to have a separated Origin parameter ? Eg: Natural/synthetic, etc, including "mixture"?

 

 

 

 

 

 

 

 

 

 

 

 

Azimuth angle in degrees - see if negative values of angles can have a special meaning

azimuth_min

environment parameters

complement incidence, emergence, and phase

 

azimuth_max

 

negative values for azi and phase have a special meaning?

 

 

 

 

 

pressure

 

unit TBC (bar in PDS speclib)

experimental conditions, in bar and K

temperature

 

K

 

measurement_atmosphere

 

description of experimental conditions, free string. Measurements under vacuum are indicated here with the word "vacuum".

 

 

 

 

 

measurement_type

relative to setup

Contains UCD for this type of spectrum

 The type of measurement/scale (REFF, I_over_F, etc…) provided as a UCD

 

 

 

Being discussed in IVOA

geometry_type

 

?

such as bidirectional, biconical, directional-hemispherical, etc - see if this list can be frozen (not likely)

spectrum_type

 

proposed to store measurement_type in clear, associated to a specific UCD (proposal to be forwarded to IVOA)

 

 

 

(may need to remove duplicates from Bernard's list)

 

 

 

 

 

sample_desc

descriptions

free string or hash-list describing the sample, its origin, and possible preparation

 free string or hash-list describing the sample, its origin, and possible preparation

setup_desc

 

free string or hash-list describing the experimental setup if needed - may include Aperture (size of sample measured), etc

 free string or hash-list describing the experimental setup if needed - may include Aperture (size of sample measured), etc

data_calibration_desc

 

free string or hash-list describing data post-processing / calibration

 free string or hash-list describing data post-processing / calibration

 

 

 

 

 

 

 

 

thumbnail_url

std parameters

provides a link to a small spectral plot for quicklook only in VESPA portal

 provides a link to a small spectral plot - caution should be taken to have units / values readable in full size (will be reduced in VESPA portal)

 

with special use

(larger plots to be provided as separated granules with dataproduct_type = im)

 

datalink_url

 

Can contain a series of links to descriptive files providing extra information (image, text…)

 Best solution to link descriptive files providing extra information

 

 

 

 

Species

 

Use it to store a chemical formula (alt: a list of atoms) - TBD

 More for basic atm in obsevational data, not used here

 

 

Comment: this parameter can be misleading if used only in some services / cases - will suggest products not found do not exist at all

 see if usage can be enlarged (e.g., to InChiKeys) - but for minerals?

species_inchikey ?

 

Check if required/useful

 

 

 

 

 

dataproduct_type

 

'sp' for spectra

 

spectral_range_min (& *_max)

 

Provide spectral range as frequency in Hz (EPNCore standard)

 

 

 

 

 

spectral_sampling_step_min (& *_max)

 

Provide sampling step as frequency in Hz (EPNCore standard)

 

spectral_resolution_min (& *_max)

 

spectral_resolution_min/max should instead provide | fq / Dfq | = | lam / Dlam |

 Provides Dfreq in EPNCore 2.0

 

 

(agree upon during workshop, but TBC with other fields)

 

 

 

 

 

Other ideas:

A parameter to identify a source database in a compilation service (such as SSHADE, or PDS speclib)

 

 

 

Photometric measurement sets?

 

 

 

Optical constants: ~ two associated spectral a single file, or one / complex type? Description / table should be identical

 

 

 

Band lists: tables with characteristics and attributions - EPNCore is not be the best solution, see later proposal

 

 

...