Instrument Parser From CSV/JSON Config - 23/07/2026 05:11 EDT

I have a stream of project-specific instrument data that must be parsed automatically according to external configuration files. The configurations come in two possible formats—CSV for quick table-style edits and JSON for more expressive rules—and I need a single parser that can load either type, interpret the rules they define, and then transform the raw incoming data into a clean, structured output (ideally a JSON object or a tidy CSV, whichever is simpler to wire into my pipeline).

Key points
• The exact instrument category is not fixed; think of it as “project-specific.” The parser therefore cannot be hard-coded to one layout. Everything about field order, data types, units, and validation thresholds has to live in the configuration files so I can tweak behaviour without touching code.
• Both configuration formats must be supported seamlessly. If you lean on a library such as pandas, Jackson, or equivalent for parsing CSV/JSON that is perfectly fine—choose whichever language and tools let you build quickly while remaining easy to hand off.
• Robust error handling is important: invalid rows should be flagged with clear messages rather than breaking the whole run.
• Deliverables: the full source code, a short README explaining how to point the parser at either a CSV or JSON config, and two tiny sample configs that prove the concept.

Once delivered, I should be able to drop in a new config file, call one command, and see my instrument data parsed exactly as described in that file—no recompilation, no edits to the core logic.