FM_fetch_mdl: Fetches Models from Modules in the App

In formods: 'Shiny' Modules for General Tasks

Fetches Models from Modules in the App

Description

Loops through each specified module ID or all modules if no ID was specified. For each ID, an attempt will be made to extract any models available.

Usage

FM_fetch_mdl(state, session, ids = NULL)

Arguments

state	Current module state after yaml file has been read
session	Shiny session variable
ids	Vector of ID strings for the modules containing models or NULL for all modules with models available.

Value

list containing the current dataset with the following format:

• isgood: General logical indicator of successfully.

• hasmdl: Logical indicating if at least one model was found.

• modules: List of module checksums.

• mdl: Result of MM_fetch_mdl, see vignette("making_modules", package = "formods")

• catalog: Dataframe containing the a tabular catalog of the models found.

  • label: Text label for the model (e.g. one-compartment model).

  • MOD_TYPE: Type of module.

  • id: Module ID.

  • rx_obj: The rxode2 object.

  • rx_obj_name: The rxode2 object name that holds the model.

  • ts_obj: List of timescale information for the system and details of other timescales (list(system="weeks", details = list(days=list(verb="days", conv=86400))))

  • ts_obj_name: The object name that holds the timescale for this model.

  • fcn_def: Text to define the model.

  • MDLMETA: Notes about the model.

  • code: Code to generate the model.

  • checksum: Module checksum.

  • MDLchecksum: Model checksum.

Examples

# We need a module state and a Shiny session variable
# to use this function:
sess_res = UD_test_mksession()
session = sess_res$session
state   = sess_res$state
mdl = FM_fetch_mdl(state, session)
mdl$catalog

formods documentation built on April 12, 2025, 1:57 a.m.