UNC Charlotte COVID-19 R19 submission#16
Conversation
Model Metadata--- UNCC-Hierbin.yaml --- ✅: [metadata_schema_exists]: File exists at path 'hub-config/model-metadata-schema.json'. ✅: [metadata_file_exists]: File exists at path 'model-metadata/UNCC-Hierbin.yaml'. ✅: [metadata_file_ext]: Metadata file extension is "yml" or "yaml". ✅: [metadata_file_location]: Metadata file directory name matches "model-metadata". ❌: [metadata_matches_schema]: Metadata file contents must be consistent with schema specifications.
|
Model Metadata--- UNCC-Hierbin.yaml --- ✅: [metadata_schema_exists]: File exists at path 'hub-config/model-metadata-schema.json'. ✅: [metadata_file_exists]: File exists at path 'model-metadata/UNCC-Hierbin.yaml'. ✅: [metadata_file_ext]: Metadata file extension is "yml" or "yaml". ✅: [metadata_file_location]: Metadata file directory name matches "model-metadata". ✅: [metadata_matches_schema]: Metadata file contents are consistent with schema specifications. ✅: [metadata_file_name]: Metadata file name matches the |
|
Good morning @lunarmouse , Thank you for your R19 submissions!
To have the latest version of the information correctly used in the validation (for example the added license), please update your forked repository, before updating your files. Please let me know if any issues or questions, Model Output--- UNCC-Hierbin/2025-04-27-UNCC-hierbin.gz.parquet --- ✅: [file_exists]: File exists at path model-output/UNCC-Hierbin/2025-04-27-UNCC-hierbin.gz.parquet. ✅: [file_name]: File name "2025-04-27-UNCC-hierbin.gz.parquet" is valid. ❗: [file_location]: File directory name must match ✅: [file_format]: File is accepted hub format. ✅: [file_n]: Number of accepted model output files per round met. ✅: [metadata_exists]: Metadata file exists at path model-metadata/UNCC-hierbin.yaml. Run validation on files: 2025-04-27-UNCC-hierbin.gz.parquet ℹ: [pairing_info]: Run grouping pairing: location, horizon, scenario_id, target, age_group; stochastic run pairing: location, horizon, scenario_id, target, age_group. Number of Samples: 100 ✅: [unique_round_id]: ✅: [match_round_id]: All ✅: [colnames]: Column names are consistent with expected round task IDs and std column names. ✅: [col_types]: Column data types match hub schema. ✅: [valid_vals]: ✅: [rows_unique]: All combinations of task ID column/ ✅: [req_vals]: Task ID/output type/output_type_id combinations all present. ✅: [value_col_valid]: Values in column ℹ: [value_col_non_desc]: No quantile or cdf output types to check for non-descending values. ℹ: [spl_non_compound_tid]: Task ID combinations of non compound task id values not tested ❗: [flat_projection]: Some projections have a unique value for the whole projection period. |
Model Metadata--- UNCC-Hierbin.yaml --- ✅: [metadata_schema_exists]: File exists at path 'hub-config/model-metadata-schema.json'. ✅: [metadata_file_exists]: File exists at path 'model-metadata/UNCC-Hierbin.yaml'. ✅: [metadata_file_ext]: Metadata file extension is "yml" or "yaml". ✅: [metadata_file_location]: Metadata file directory name matches "model-metadata". ✅: [metadata_matches_schema]: Metadata file contents are consistent with schema specifications. ✅: [metadata_file_name]: Metadata file name matches the |
Model Output--- UNCC-Hierbin/2025-04-27-UNCC-Hierbin.gz.parquet --- ✅: [file_exists]: File exists at path 'model-output/UNCC-Hierbin/2025-04-27-UNCC-Hierbin.gz.parquet'. ✅: [file_name]: File name "2025-04-27-UNCC-Hierbin.gz.parquet" is valid. ✅: [file_location]: File directory name matches ✅: [round_id_valid]: ✅: [file_format]: File is accepted hub format. ✅: [file_n]: Number of accepted model output files per round met. ✅: [metadata_exists]: Metadata file exists at path 'model-metadata/UNCC-Hierbin.yaml'. Run validation on files: 2025-04-27-UNCC-Hierbin.gz.parquet ℹ: [pairing_info]: Run grouping pairing: location, horizon, scenario_id, target, age_group; stochastic run pairing: location, horizon, scenario_id, target, age_group. Number of Samples: 100 ✅: [unique_round_id]: ✅: [match_round_id]: All ✅: [colnames]: Column names are consistent with expected round task IDs and std column names. ✅: [col_types]: Column data types match hub schema. ✅: [valid_vals]: ✅: [rows_unique]: All combinations of task ID column/ ✅: [req_vals]: Task ID/output type/output_type_id combinations all present. ✅: [value_col_valid]: Values in column ℹ: [value_col_non_desc]: No quantile or cdf output types to check for non-descending values. ℹ: [spl_non_compound_tid]: Task ID combinations of non compound task id values not tested ❗: [flat_projection]: Some projections have a unique value for the whole projection period. |
|
Good morning @lunarmouse , Thank you for the update! The validation has run, however the abstract still have some issues.
Please let me know if any issues or questions, |
|
Thanks Lucie! I have moved the abstract to the correct folder, and renamed it. The pairing information in the main result parquet file is correct. As for the flat predictions of deaths in some states, I double checked the historical data, it could be caused by extended period of 0 deaths in these states. Therefore, the model just tried to "mimic" the pattern by generating a flat prediction as well. Since the historical and predicted death numbers are extremely low, I would not add some random noise around the predictions. Best regards, Shi |
|
Just for information, I updated the format of the Best, Lucie |
|
Thank you for your help, Lucie. Appreciate it. Have a great weekend, Shi |
With the requested result file and metadata.