Science Score: 67.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
✓DOI references
Found 5 DOI reference(s) in README -
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (11.4%) to scientific vocabulary
Repository
Technical validation code for the TOCOM dataset
Basic Info
- Host: GitHub
- Owner: spartanjoax
- License: agpl-3.0
- Language: Python
- Default Branch: main
- Size: 70.3 KB
Statistics
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 3
Metadata Files
README.md
Description
This repository provides the technical validation scripts for the Mondragon Unibertsitatea tool condition monitoring (MU-TCM) face-milling dataset, enabling reproducible data processing, synchronisation, and feature extraction for TCM in milling processes.
Acknowledgements
This work was developed at the Software and systems engineering and the High-performance machining groups at Mondragon University, as part of the Digital Manufacturing and Design Training Network.
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under the Marie Skłodowska-Curie grant agreement No 814078 (DIMAND) and by the Department of Education, Universities and Research of the Basque Government under the projects Ikerketa Taldeak (Grupo de Ingeniería de Software y Sistemas IT1519-22 and Grupo de investigación de Mecanizado de Alto Rendimiento IT1443-22).
Installation
- Fork the project.
- Clone the project.
- Install requirements with PIP
bash pip install -r requirements.txt - Follow the instructions in the Usage section.
Usage
This code is meant to be used alongside the MU-TCM face-milling dataset. This repository provides three main scripts to process and evaluate the dataset. Below are the instructions for each script:
- Signal_sync.py: This script handles the synchronisation of internal and external signals, aligning them based on peak analysis to ensure that all data sources are accurately aligned for further analysis.
bash
python Signal_sync.py --input_dir <path_to_raw_data> --output_dir <path_to_synced_data>
- --input_dir: Path to the directory containing the unsynchronised signal data. Default value is ../signals_unsynced.
- --output_dir: Path to the directory where synchronised data will be saved. Default value is ../signals_synced. A CSV file (signals_sync.csv) with the synchronisation selections is saved also in this directory upon script completion.
- Signalfeatureextraction.py: This script performs feature extraction on the synchronised signals, generating time, frequency, and time-frequency-domain features (e.g., RMS, kurtosis, peak-to-peak, wavelet energy) that can be used for TCM.
bash
python Signal_feature_extraction.py --input_dir <path_to_synced_data>
- --input_dir: Path to the directory containing synchronised signal data. Default value is ../signals_synced. A CSV file (signals_stats.csv) with the extracted features is saved in this directory upon script completion.
- Signal_evaluator.py: This script evaluates the extracted features against tool wear annotations, providing insights into which features show strong correlations with tool wear, and is useful for understanding the most relevant metrics for TCM.
bash
python Signal_evaluator.py --features_path <path_to_features_file>
- --features_path: Path to the file containing the extracted features. Default value is ../signals_synced/signals_stats.csv.
Example Workflow
- Step 1: Synchronise Signals
Run Signal_sync.py to align raw signals from different sources, creating synchronised files ready for feature extraction.
- Step 2: Extract Features
Use Signalfeatureextraction.py to process synchronised signals and extract a range of relevant features.
- Step 3: Evaluate Features
Finally, apply Signal_evaluator.py to analyze the extracted features against tool wear data, identifying metrics most associated with tool wear progression.
This sequence allows users to go from raw data to insights on the most relevant features for TCM in milling processes.
Contributors
Cite
If you use this code in your own work, please use the following bibtex entries:
```bibtex @software{PeraltaAbadiaMU-TCM_2024, author = {Peralta Abadia, Jose Joaquin and Cuesta Zabaljauregui, Mikel and Larrinaga Barrenechea, Felix}, license = {AGPL-3.0}, month = mar, title={{Technical validation code for the MU-TCM face-milling dataset}}, url = {https://github.com/spartanjoax/MU-TCM}, version = {1.2}, year = {2025}, publisher = {Zenodo}, doi={https://doi.org/10.5281/zenodo.14012462} }
@article{peralta2025tocomon, title={{Mondragon Unibertsitatea face-milling dataset for smart tool condition monitoring}}, author={Peralta Abadia, Jose Joaquin and Cuesta Zabaljauregui, Mikel and Larrinaga Barrenechea, Felix}, journal={...pending...}, year={2025} } ```
Owner
- Login: spartanjoax
- Kind: user
- Repositories: 1
- Profile: https://github.com/spartanjoax
Citation (CITATION.cff)
# This CITATION.cff file was generated with cffinit.
# Visit https://bit.ly/cffinit to generate yours today!
cff-version: 1.2.0
title: Technical validation code for the MU-TCM face-milling dataset
message: >-
If you use this software, please cite it using the
metadata from this file.
type: software
authors:
- given-names: Jose Joaquin
family-names: Peralta Abadia
orcid: 'https://orcid.org/0000-0003-0261-6792'
- given-names: Mikel
family-names: Cuesta Zabaljauregui
orcid: 'https://orcid.org/0000-0001-6419-5394'
- given-names: Felix
family-names: Larrinaga Barrenechea
orcid: 'https://orcid.org/0000-0003-1971-0048'
identifiers:
- type: doi
value: 10.5281/zenodo.14012462
repository-code: 'https://github.com/spartanjoax/MU-TCM'
license: AGPL-3.0
version: '1.2'
date-released: '2025-03-24'
GitHub Events
Total
- Release event: 6
- Push event: 9
- Fork event: 1
- Create event: 3
Last Year
- Release event: 6
- Push event: 9
- Fork event: 1
- Create event: 3