Versions Compared

Key

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

Page Navigation:

Table of Contents
outlinetrue
stylecircle

(blue star) Confidence Level Moderate  This article includes input from several JPLers. Multiple subject matter experts can indicate that a page is more frequently reviewed and updated.


This article provides a brief overview of the .JSON log files found in each completed science product produced by HySDS. These files are located at the root directory of the worker node.

The Elasticsearch database is built by combining info from _context.json, _met.json, and _dataset.json. In a working directory this is among the bare minimum required for HySDS to recognize it as a valid dataset. There may be additional information, but this is the essentials.

The three main log files are:

_context.json

This file provides a unique “recipe” for each job. Once a job is picked up by a Verdi worker, the _context.json file is updated as it proceeds through the job life cycle. The file is updated again when the job reached either job-failed or job-complete status.

As part of the final job state transition, the _context.json file is is indexed into Elasticsearch. The file includes: job priority, job specs, parameters, etc.

_met.json 

This file is specific to HySDS, and includes three basic elements of a dataset, such as: start time, end time, and location.

Info

Note: the left side of of the Facet Search Page menu (Tosca) is populated using metadata, and varies by adaptation.

_dataset.json

This file includes: label, start time, and version.


(lightbulb) Have Questions? Ask a HySDS Developer:

Anyone can join our public Slack channelto learn more about HySDS.

JPL employees can join #HySDS-Community

(blue star)

JPLers can also ask HySDS questions atStack Overflow Enterprise

(blue star)

Live Search
placeholderSearch HySDS Wiki