There could be several reasons you are having issues with your INP files:
- Your INP doesn't contain tanks or supply sources, or your assets are not connected to them.
- Qatium accepts only valid .inp files per EPANET 2.2 standards. If your .inp file runs in EPANET 2.2 but the problem persists, we’ll review the model and make the adjustments for it to work.
- The asset IDs are too long. Qatium and EPANET 2.2 only support 31-character IDs, so if you are exporting from EPANET 2.0 or other software vendors to .inp, make sure IDs don't exceed that length.
- You've tried to upload multiple INP files simultaneously. We only admit 1 INP file at a time. If you dropped several INP and/or Signal Mapping files into Qatium, we’ll only process the first we receive one and ignore the rest.
If you need help, please contact us.