Experimental collaboration
The current bottleneck is data
Software development is not a prerequisite for collaboration. The immediate need is experimentally grounded information capable of constraining, calibrating and validating the models.
Machine information
- machine architecture
- electrical characteristics
- electrode or jaw geometry
- motion systems
- force capabilities
- control strategies
Process histories
- current and voltage
- stage timing
- flashing parameters
- burn-off or displacement
- upset force
- pre- and post-heating sequences
Material and validation data
- temperature-dependent properties
- thermal and electrical properties
- mechanical properties
- metallography
- hardness maps
- temperature histories
- mechanical-test results
Questions already sent
Examples of targeted research questions
Researchers have already been approached with questions derived from their published work. The examples below are anonymized and illustrate the type of scientific exchange sought by the project.
- Can measured welding thermal cycles be shared as numerical time–temperature series rather than only as plotted figures?
- Can representative process schedules, stage boundaries, electrical signals, displacement or burn-off histories be made available in processed, anonymized or stage-averaged form?
- Which observables are most reliable for validating a reduced flash-butt-welding model when direct interface measurements are unavailable?
- Which material-state variables and phase-transformation data should a reusable material library prioritize, and how should material properties be separated from process-specific calibration?
Data ownership, redistribution rights and publication permissions are treated independently. Scientific use does not automatically imply permission to publish raw data.
Contributions may lead to formal project participation and, where the scientific contribution justifies it, co-authorship of resulting publications.