Model file validation checks have been a part of the corresponding csv to binary conversion tools since ktools v3.12.0 (see PR https://github.com/OasisLMF/ktools/pull/370). Currently, when using footprinttobin to convert footprint csv files to binary format, there is no check that event ID does not exceed the MAX_INT limit. This can lead to negative event IDs as a result of integer overflow, or even more dangerously positive event IDs that are reported as being 232 less than that in the csv file.
A check for this should be introduced in a similar fashion to the check on vulnerability ID in vulnerabilitytobin.
Issue Description
Model file validation checks have been a part of the corresponding csv to binary conversion tools since ktools v3.12.0 (see PR https://github.com/OasisLMF/ktools/pull/370). Currently, when using
footprinttobinto convert footprint csv files to binary format, there is no check that event ID does not exceed the MAX_INT limit. This can lead to negative event IDs as a result of integer overflow, or even more dangerously positive event IDs that are reported as being 232 less than that in the csv file.A check for this should be introduced in a similar fashion to the check on vulnerability ID in
vulnerabilitytobin.Version / Environment information
ktools >v3.12.0