clustered-peak-output-formatting
Summary
Export clustered peak networks from pyINETA's clustering module into formats compatible with downstream metabolite matching and database lookup. This skill standardizes peak-to-cluster assignments and metadata for seamless integration with the matching and finding modules.
When to use
After peak clustering has been completed in pyINETA (i.e., after peaks have been grouped into networks based on spectral similarity and co-occurrence patterns) and you need to prepare the clustered data for matching against a simulated INADEQUATE metabolite database or other downstream analysis steps.
When NOT to use
- Peak clustering has not yet been performed; use peak picking output directly instead.
- Peaks have not been grouped into networks; output formatting assumes valid cluster assignments exist.
- You intend to perform further clustering refinement; export only after final clustering decisions are made.
Inputs
- Clustered peak assignments (peak identifiers with cluster membership labels)
- Peak attributes from clustering output (chemical shifts, intensities, co-occurrence patterns)
- Peak-to-cluster mapping data structure from pyINETA.clustering module
Outputs
- Formatted peak-cluster mapping file (e.g., CSV with peak ID, cluster ID, and peak attributes)
- Clustered peak data compatible with pyINETA matching module input format
- Cluster network metadata documentation
How to apply
After applying pyINETA's clustering algorithm to group picked peaks into networks, generate a mapping file that documents peak-to-cluster assignments, with each peak assigned a unique cluster identifier. Export the clustered peak data in a structured format (e.g., CSV or tabular format compatible with pyINETA's matching module input specification) that preserves peak attributes (chemical shifts, intensities, cluster membership) and maintains the data schema required by downstream modules. Validate that all peaks from the input clustering step appear in the output and that cluster identifiers are consistent and traceable. The export format must be compatible with the matching module's input interface to ensure uninterrupted workflow execution.
Related tools
- PyINETA (Source framework providing clustering module (pyineta.clustering) and matching module input specification for formatted output) — https://github.com/edisonomics/PyINETA
- Python (Implementation language for data serialization, format conversion, and output file generation)
Examples
python <path_to_pyineta_repo>/run_pyineta.py -c config.ini -s cluster -o output_folder
Evaluation signals
- All peaks from the clustering input appear in the output mapping with valid cluster identifiers and no missing entries.
- Cluster identifiers are unique, consistent, and traceable across the output file.
- Peak attributes (chemical shifts, intensities) are preserved and match the input values from the clustering module.
- Output file format matches the input schema expected by the pyINETA matching module (e.g., column names, data types, delimiters).
- Downstream matching module accepts the formatted output without schema validation errors.
Limitations
- Output format is specific to pyINETA's matching module specification; reformatting may be required for use with external matching tools.
- No changelog or versioning guidance is provided; format compatibility across pyINETA versions is not documented.
- The skill assumes clustering has already assigned cluster identifiers; malformed or missing cluster assignments will propagate to the output.
Evidence
- [other] Export the clustered peak data in a format compatible with downstream matching and finding modules.: "Export the clustered peak data in a format compatible with downstream matching and finding modules."
- [other] Assign each peak a cluster identifier and generate a mapping file documenting peak-to-cluster assignments.: "Assign each peak a cluster identifier and generate a mapping file documenting peak-to-cluster assignments."
- [readme] It is designed to filter these picked peaks to identify networks of peaks (ideally) coming from the same compound which it then matches to a simulated INADEQUATE database of metabolites to identify metabolites present in the query INADEQUATE spectra.: "filter these picked peaks to identify networks of peaks (ideally) coming from the same compound which it then matches to a simulated INADEQUATE database"
- [other] pyINETA implements a clustering module that filters picked peaks to identify networks of peaks from the same compound, operating as a downstream step after peak picking and before matching to metabolite databases.: "clustering module that filters picked peaks to identify networks of peaks from the same compound, operating as a downstream step after peak picking and before matching"
1---2name: clustered-peak-output-formatting3description: Use when after peak clustering has been completed in pyINETA (i.4license: CC-BY-4.05---67# clustered-peak-output-formatting89## Summary1011Export clustered peak networks from pyINETA's clustering module into formats compatible with downstream metabolite matching and database lookup. This skill standardizes peak-to-cluster assignments and metadata for seamless integration with the matching and finding modules.1213## When to use1415After peak clustering has been completed in pyINETA (i.e., after peaks have been grouped into networks based on spectral similarity and co-occurrence patterns) and you need to prepare the clustered data for matching against a simulated INADEQUATE metabolite database or other downstream analysis steps.1617## When NOT to use1819- Peak clustering has not yet been performed; use peak picking output directly instead.20- Peaks have not been grouped into networks; output formatting assumes valid cluster assignments exist.21- You intend to perform further clustering refinement; export only after final clustering decisions are made.2223## Inputs2425- Clustered peak assignments (peak identifiers with cluster membership labels)26- Peak attributes from clustering output (chemical shifts, intensities, co-occurrence patterns)27- Peak-to-cluster mapping data structure from pyINETA.clustering module2829## Outputs3031- Formatted peak-cluster mapping file (e.g., CSV with peak ID, cluster ID, and peak attributes)32- Clustered peak data compatible with pyINETA matching module input format33- Cluster network metadata documentation3435## How to apply3637After applying pyINETA's clustering algorithm to group picked peaks into networks, generate a mapping file that documents peak-to-cluster assignments, with each peak assigned a unique cluster identifier. Export the clustered peak data in a structured format (e.g., CSV or tabular format compatible with pyINETA's matching module input specification) that preserves peak attributes (chemical shifts, intensities, cluster membership) and maintains the data schema required by downstream modules. Validate that all peaks from the input clustering step appear in the output and that cluster identifiers are consistent and traceable. The export format must be compatible with the matching module's input interface to ensure uninterrupted workflow execution.3839## Related tools4041- **PyINETA** (Source framework providing clustering module (pyineta.clustering) and matching module input specification for formatted output) — https://github.com/edisonomics/PyINETA42- **Python** (Implementation language for data serialization, format conversion, and output file generation)4344## Examples4546```47python <path_to_pyineta_repo>/run_pyineta.py -c config.ini -s cluster -o output_folder48```4950## Evaluation signals5152- All peaks from the clustering input appear in the output mapping with valid cluster identifiers and no missing entries.53- Cluster identifiers are unique, consistent, and traceable across the output file.54- Peak attributes (chemical shifts, intensities) are preserved and match the input values from the clustering module.55- Output file format matches the input schema expected by the pyINETA matching module (e.g., column names, data types, delimiters).56- Downstream matching module accepts the formatted output without schema validation errors.5758## Limitations5960- Output format is specific to pyINETA's matching module specification; reformatting may be required for use with external matching tools.61- No changelog or versioning guidance is provided; format compatibility across pyINETA versions is not documented.62- The skill assumes clustering has already assigned cluster identifiers; malformed or missing cluster assignments will propagate to the output.6364## Evidence6566- [other] Export the clustered peak data in a format compatible with downstream matching and finding modules.: "Export the clustered peak data in a format compatible with downstream matching and finding modules."67- [other] Assign each peak a cluster identifier and generate a mapping file documenting peak-to-cluster assignments.: "Assign each peak a cluster identifier and generate a mapping file documenting peak-to-cluster assignments."68- [readme] It is designed to filter these picked peaks to identify networks of peaks (ideally) coming from the same compound which it then matches to a simulated INADEQUATE database of metabolites to identify metabolites present in the query INADEQUATE spectra.: "filter these picked peaks to identify networks of peaks (ideally) coming from the same compound which it then matches to a simulated INADEQUATE database"69- [other] pyINETA implements a clustering module that filters picked peaks to identify networks of peaks from the same compound, operating as a downstream step after peak picking and before matching to metabolite databases.: "clustering module that filters picked peaks to identify networks of peaks from the same compound, operating as a downstream step after peak picking and before matching"
HolobiomicsLab 