Skip to contents

Check model output data tbl samples contain single unique values for each compound task ID within individual samples

Source: R/check_tbl_spl_compound_tid.R
check_tbl_spl_compound_tid.Rd

Check model output data tbl samples contain single unique values for each compound task ID within individual samples

Usage

check_tbl_spl_compound_tid(tbl, round_id, file_path, hub_path)

Arguments

tbl

a tibble/data.frame of the contents of the file being validated. Column types must all be character.

round_id

character string. The round identifier.

file_path

character string. Path to the file being validated relative to the hub's model-output directory.

hub_path

Either a character string path to a local Modeling Hub directory or an object of class <SubTreeFileSystem> created using functions s3_bucket() or gs_bucket() by providing a string S3 or GCS bucket name or path to a Modeling Hub directory stored in the cloud. For more details consult the Using cloud storage (S3, GCS) in the arrow package. The hub must be fully configured with valid admin.json and tasks.json files within the hub-config directory.

Value

Depending on whether validation has succeeded, one of:

  • <message/check_success> condition class object.

  • <error/check_error> condition class object.

Returned object also inherits from subclass <hub_check>.

Details

Output of the check includes an errors element, a list of items, one for each sample failing validation, with the following structure:

  • mt_id: Index identifying the config modeling task the sample is associated with.

  • output_type_id: The output type ID of the sample that does not contain a single, unique value for each compound task ID.

  • values: The unique values of each compound task ID. See hubverse documentation on samples for more details.