Create a new Parser Definition from the Signals Configuration

For Administrators only.

Prior to this task: 

✔ Data file(s) must be available locally. 

*Required.

1️⃣ Signals Configuration ➡ select [Parser Definitions]
2️⃣ Parser Definitions ➡ select [Parser Definition] ➡ select Create
3️⃣ Create Parser Definition ➡ type Name* Description
4️⃣ Create Parser Definition ➡ select [Create]
5️⃣ Parser Definition ➡ select [Select file]
6️⃣ Open window ➡ browse and select data file(s)
7️⃣ Open window ➡ select [Open]
8️⃣ Parser Definition ➡ select/type Data format Well values Layout Worksheets Name Worksheets Positions Primary Delimiter Secondary Delimiter Filename Delimiter Plate Rows Plate Columns Starting Keyword File Header Rows Plate Header Rows Data Block Headers Rows Data Block Column Headers Data Blocks Per Plate Data Block Footer Rows Plate Footer Rows File Footer Rows
9️⃣ Parser Definition ➡ Columns ➡ modify accordingly
🔟 Parser Definition ➡ select [Save]

Supporting Knowledge

Optionally, after a Parser Definition has been created, modification may be required while the original is preserved. To create a working copy, from the Parser Definitions page, select the desired Parser Definition. From the selected Parser Definition, select the [Actions] button, then select Download. Open the downloaded JSON file using a text editor (such as Notepad or Visual Studio Code) and update the name field to reflect the new version before the file is saved. Return to the Parser Definitions page and select the [Parser Definition] button, then select Import from File. From the Open window, select the modified JSON file that was saved. Finally, from the newly imported Parser Definition, all necessary adjustments should be implemented, and the updated Parser Definition should be saved.

⚠️ Important: The original Parser Definition should not be edited directly without first creating a copy, as the existing configuration will be permanently overwritten. A duplicate should always be created before any modifications are made.

Alternative Approaches

• If multiple file formats are exported by an instrument, separate Parser Definitions should be created for each format rather than attempting to handle all variations within a single parser.
• For instruments with frequently changing output formats, versioned parsers are recommended (e.g., 'InstrumentName_v1', 'InstrumentName_v2').