Parameters and omega and sigma matrices that were imported via $NMXML
or $NMEXT
will be written into the yaml file and the NONMEM import blocks
will be dropped. This allows the user to load a model based on a NONMEM run
without having a connection to that output (e.g., root.xml
or root.ext
).
Given that the connection to the NONMEM modeling outputs is broken when
writing to yaml, any update to the NONMEM run will only be propagated to
the yaml file when mwrite_yaml()
is run again.
The yaml file does not currently have the ability to track
other external dependencies, such as user-defined header files or other
code that might be sourced in by the user when the model is loaded via
mread()
. NONMEM xml and ext files imported by $NMXML
or $NMEXT
are
the only external dependencies that are accounted for in the yaml
transport file.