Skip to content

Latest commit

 

History

History
143 lines (113 loc) · 6.32 KB

README.md

File metadata and controls

143 lines (113 loc) · 6.32 KB
Raw

scicat-filewriter-ingest

this project listen to the kafka topic command_channel.
when a new file is written to the file server by the file writer
it interface with scicat and create a raw dataset

important messages to listen to are:

This is the structure of the two messages as listed in the links above:

run start

RunStart {                                     //  *Mantid*    // *File Writer* // *Description*
    start_time : uint64;                             //  Required    //  Optional     // milliseconds since Unix epoch (1 Jan 1970)
    stop_time : uint64;                              //  Unused      //  Optional     // milliseconds since Unix epoch (1 Jan 1970), optional, can send a RunStop instead
    run_name : string;                               //  Required    //  Unused       // Name for the run, used as workspace name by Mantid
    instrument_name : string;                        //  Required    //  Unused       // Name of the instrument, only required by Mantid
    nexus_structure : string;                        //  Optional    //  Required     // JSON description of NeXus file (See https://github.com/ess-dmsc/kafka-to-nexus/ for detail)
                                                                                      // If present Mantid will parse this to get the instrument geometry, otherwise it will attempt
                                                                                      // to look up an Instrument Definition File (IDF) based on the instrument name
    job_id : string;                                 //  Unused      //  Required     // A unique identifier for the file writing job
    broker : string;                                 //  Unused      //  Required     // Broker name and port, for example "localhost:9092", from which the file writer should get data
    service_id : string;                             //  Unused      //  Optional     // The identifier for the instance of the file-writer that should handle this command
    filename : string;                               //  Unused      //  Required     // Name of the file to write, for example run_1234.nxs
    n_periods : uint32 = 1;                          //  Optional    //  Unused       // Number of periods (ISIS only)
                                                                                      // Periods provide a way to segregate data at the data acquisition stage
    detector_spectrum_map: SpectraDetectorMapping;   //  Optional    //  Unused       // Map spectrum numbers in the event messages to detector IDs in the instrument definition (optional, for ISIS only)
    metadata : string;                               //  Unused      //  Optional     // Holds a JSON string with (static) metadata about the measurement. E.g. proposal id.
}

finished writing

table FinishedWriting {
    service_id : string (required);     // milliseconds since Unix epoch (1 Jan 1970). When set to 0, will trigger a "stop NOW" code path in the file writer.
    job_id : string (required);         // The unique identifier of the file writing job
    error_encountered : bool;           // True if stopped due to error
    file_name : string (required);      // Name of file that was just closed.
    metadata : string;                  // JSON string with metadata about the file that was just closed.
    message : string;                   // Must hold an error message if filewriting was stopped due to an error, is optional otherwise.
}

We need to decide if we are going to listen only to "finished writing" or also to "run start" and populate the scicat metadata from both.

There are few libraries already available that can be used to list and interpret the messages received:

Following is an example of a listener code:

This link provide a lot of information regarding the setup of the kafka cluster and broker:

In the folder examples/producer, a file producer application is provided to test the consumer

Installation

If you are using conda, following are the instruction on how to set up the scicat filewriter ingestor:

  • clone the code repository

    > git clone https://gitlab.esss.lu.se/swap/scicat-filewriter-ingest.git scicat-filewriter-ingest

  • step in to the folder

    > cd scicat-filewriter-ingest

  • checkout current version, which at the moment is v1.0.0

    > git checkout v1.0.0

  • create conda environment

    > conda env create -f requirements-SFI.yml

  • activate the conda environment

    > conda activate SFI

  • prepare the configuration file. You can copy the example provided in the repo and customize it to your needs.

    > cp config.sample.json config.json

  • start the ingestor. The application will read automatically the config file.

    > ./scicat_ingestor.py

    if you want logging to the console and to the syslog

    > ./scicat_ingestor.py -v --sys-log

If you prefer to use straight python with pip, these are the instructions for you:

  • make sure that you have python 3.8.x or higher

  • make sure that pip is installed

  • clone the code repository

    > git clone https://gitlab.esss.lu.se/swap/scicat-filewriter-ingest.git scicat-filewriter-ingest

  • step in to the folder

    > cd scicat-filewriter-ingest

  • checkout current version, which at the moment is v1.0.0

    > git checkout v1.0.0

  • install the required packages

    > pip install -f requirements_SFI.txt

  • prepare the configuration file. You can copy the example provided in the repo and customize it to your needs.

    > cp config.sample.json config.20230125.json

  • start the ingestor. The application will read automatically the config file.

    > ./scicat_ingestor.py

    if you want logging to the console and to the syslog

    > ./scicat_ingestor.py -v --sys-log