Writing data to files#> [1] "DataPrepare.Rmd"
#>
#> $dataCreate$CreationTime
-#> [1] "2024-10-30 13:46:41 UTC"
+#> [1] "2024-10-30 14:58:39 UTC"
#>
#> $dataCreate$writtenTo
#> [1] "derived/pkdata.rds" "derived/pkdata.csv"
@@ -858,7 +858,7 @@ Stamp objects for traceability#> [1] "vignettes/DataCreate.Rmd"
#>
#> $dataCreate$CreationTime
-#> [1] "2024-10-30 13:46:41 UTC"
+#> [1] "2024-10-30 14:58:39 UTC"
The script argument is recognized by
NMstamp, but you can add anything to this. We want to keep
descriptive note too. Another often useful piece of information is what
@@ -874,7 +874,7 @@
Stamp objects for traceability#> [1] "vignettes/DataCreate.Rmd"
#>
#> $dataCreate$CreationTime
-#> [1] "2024-10-30 13:46:41 UTC"
+#> [1] "2024-10-30 14:58:39 UTC"
#>
#> $dataCreate$Description
#> [1] "A PK dataset used for examples."
diff --git a/articles/NMdata-cheat.html b/articles/NMdata-cheat.html
index 0d9e4c3d..97aeaa73 100644
--- a/articles/NMdata-cheat.html
+++ b/articles/NMdata-cheat.html
@@ -323,10 +323,10 @@ Debugging input data (and contr
res.debug$tables
#> source name nrow ncol nid filetype file.mtime
#> <char> <char> <int> <int> <int> <char> <POSc>
-#> 1: input pkdata.csv 1502 23 150 csv 2024-10-30 13:46:44
+#> 1: input pkdata.csv 1502 23 150 csv 2024-10-30 14:58:42
#> file.logtime file has.col.row
#> <char> <char> <lgcl>
-#> 1: 2024-10-30 13:46:44.829605 nonmem/../derived/pkdata.csv TRUE
+#> 1: 2024-10-30 14:58:42.555296 nonmem/../derived/pkdata.csv TRUE
#> has.col.id
#> <lgcl>
#> 1: TRUE
@@ -479,7 +479,7 @@ Traceability#> [1] "NMdata-cheat.Rmd"
#>
#> $CreationTime
-#> [1] "2024-10-30 13:46:44.829605"
+#> [1] "2024-10-30 14:58:42.555296"
#>
#> $writtenTo
#> [1] "derived/pkdata.rds derived/pkdata.csv"
diff --git a/index.html b/index.html
index 2ab39f18..eceb60c4 100644
--- a/index.html
+++ b/index.html
@@ -107,7 +107,7 @@
-NMdata
+
@@ -129,24 +129,25 @@ NMdata is not a silo
More information
-The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
+The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
-
-
+
+
How to install
NMdata is on CRAN and MPN. To install from the package archive you are already using, do:
-
+
+install.packages("NMdata")
+library(NMdata)
See further below for instructions on how to install from other sources than your default archive, if need be.
Prepare, check, and export PK/PD data
-On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
+On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
Check data as read by NONMEM
@@ -195,7 +196,7 @@ Automated and gener
NMdataConf(as.fun="data.table")
res.dt <- NMscanData("xgxr001.lst",quiet=TRUE)
-
NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
+NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
Meta analysis made really easy
@@ -216,7 +217,7 @@ Meta analysis made really easy#> Warning: Transformation introduced infinite values in continuous y-axis
#> Warning: Transformation introduced infinite values in continuous y-axis
-
+
Get the most recent version
@@ -228,24 +229,24 @@ Get the most recent version
## Option 3: Install from github
library(remotes)
-install_github("philipdelff/NMdata")
+install_github("nmautoverse/NMdata")
library(NMdata)
-If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
+If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
Issues?
-The best way to report a bug or to request features is on github.
+The best way to report a bug or to request features is on github.
Code of Conduct
-Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
+Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
@@ -295,8 +296,8 @@ Developers
Dev status
diff --git a/pkgdown.yml b/pkgdown.yml
index 59acfb8e..7b50c614 100644
--- a/pkgdown.yml
+++ b/pkgdown.yml
@@ -7,7 +7,7 @@ articles:
NMdata-FAQ: NMdata-FAQ.html
NMscanData: NMscanData.html
ParameterTables: ParameterTables.html
-last_built: 2024-10-30T13:46Z
+last_built: 2024-10-30T14:58Z
urls:
reference: https://nmautoverse.github.io/NMdata/reference
article: https://nmautoverse.github.io/NMdata/articles
diff --git a/reference/NMdataConf.html b/reference/NMdataConf.html
index 04e7d9d4..9f57de6b 100644
--- a/reference/NMdataConf.html
+++ b/reference/NMdataConf.html
@@ -273,7 +273,7 @@ Examples
#> return(as.data.frame(list()))
#> UseMethod("as.data.frame")
#> }
-#> <bytecode: 0x555b11fa7578>
+#> <bytecode: 0x5589109e5260>
#> <environment: namespace:base>
#>
#> $check.time
@@ -311,32 +311,32 @@ Examples
#> {
#> fnExtension(file, ext = ".ext")
#> }
-#> <bytecode: 0x555b1223c698>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x5589109ffeb0>
+#> <environment: 0x5589109e4930>
#>
#> $file.cov
#> function (file)
#> {
#> fnExtension(file, ext = ".cov")
#> }
-#> <bytecode: 0x555b1223bfd0>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x5589109ff7e8>
+#> <environment: 0x5589109e4930>
#>
#> $file.phi
#> function (file)
#> {
#> fnExtension(file, ext = ".phi")
#> }
-#> <bytecode: 0x555b120ce868>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a02f50>
+#> <environment: 0x5589109e4930>
#>
#> $file.shk
#> function (file)
#> {
#> fnExtension(file, ext = ".shk")
#> }
-#> <bytecode: 0x555b120ce1a0>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a02888>
+#> <environment: 0x5589109e4930>
#>
#> $file.mod
#> function (file)
@@ -350,8 +350,8 @@ Examples
#> }
#> ctl
#> }
-#> <bytecode: 0x555b120cdad8>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a021c0>
+#> <environment: 0x5589109e4930>
#>
#> $file.data
#> [1] "extract"
@@ -362,8 +362,8 @@ Examples
#> $modelname
#> function (file)
#> fnExtension(basename(file), "")
-#> <bytecode: 0x555b120d0a98>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a070a0>
+#> <environment: 0x5589109e4930>
#>
#> $nc
#> [1] 64
diff --git a/reference/NMstamp.html b/reference/NMstamp.html
index 6bd1eb18..249636a1 100644
--- a/reference/NMstamp.html
+++ b/reference/NMstamp.html
@@ -145,7 +145,7 @@ Examples
#> [1] "example.R"
#>
#> $dataCreate$CreationTime
-#> [1] "2024-10-30 13:46:31 UTC"
+#> [1] "2024-10-30 14:58:28 UTC"
#>
#> $dataCreate$description
#> [1] "Example data"
The script argument is recognized by
NMstamp, but you can add anything to this. We want to keep
descriptive note too. Another often useful piece of information is what
@@ -874,7 +874,7 @@
Stamp objects for traceability#> [1] "vignettes/DataCreate.Rmd"
#>
#> $dataCreate$CreationTime
-#> [1] "2024-10-30 13:46:41 UTC"
+#> [1] "2024-10-30 14:58:39 UTC"
#>
#> $dataCreate$Description
#> [1] "A PK dataset used for examples."
diff --git a/articles/NMdata-cheat.html b/articles/NMdata-cheat.html
index 0d9e4c3d..97aeaa73 100644
--- a/articles/NMdata-cheat.html
+++ b/articles/NMdata-cheat.html
@@ -323,10 +323,10 @@ Debugging input data (and contr
res.debug$tables
#> source name nrow ncol nid filetype file.mtime
#> <char> <char> <int> <int> <int> <char> <POSc>
-#> 1: input pkdata.csv 1502 23 150 csv 2024-10-30 13:46:44
+#> 1: input pkdata.csv 1502 23 150 csv 2024-10-30 14:58:42
#> file.logtime file has.col.row
#> <char> <char> <lgcl>
-#> 1: 2024-10-30 13:46:44.829605 nonmem/../derived/pkdata.csv TRUE
+#> 1: 2024-10-30 14:58:42.555296 nonmem/../derived/pkdata.csv TRUE
#> has.col.id
#> <lgcl>
#> 1: TRUE
@@ -479,7 +479,7 @@ Traceability#> [1] "NMdata-cheat.Rmd"
#>
#> $CreationTime
-#> [1] "2024-10-30 13:46:44.829605"
+#> [1] "2024-10-30 14:58:42.555296"
#>
#> $writtenTo
#> [1] "derived/pkdata.rds derived/pkdata.csv"
diff --git a/index.html b/index.html
index 2ab39f18..eceb60c4 100644
--- a/index.html
+++ b/index.html
@@ -107,7 +107,7 @@
-NMdata
+
@@ -129,24 +129,25 @@ NMdata is not a silo
More information
-The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
+The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
-
-
+
+
How to install
NMdata is on CRAN and MPN. To install from the package archive you are already using, do:
-
+
+install.packages("NMdata")
+library(NMdata)
See further below for instructions on how to install from other sources than your default archive, if need be.
Prepare, check, and export PK/PD data
-On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
+On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
Check data as read by NONMEM
@@ -195,7 +196,7 @@ Automated and gener
NMdataConf(as.fun="data.table")
res.dt <- NMscanData("xgxr001.lst",quiet=TRUE)
-
NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
+NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
Meta analysis made really easy
@@ -216,7 +217,7 @@ Meta analysis made really easy#> Warning: Transformation introduced infinite values in continuous y-axis
#> Warning: Transformation introduced infinite values in continuous y-axis
-
+
Get the most recent version
@@ -228,24 +229,24 @@ Get the most recent version
## Option 3: Install from github
library(remotes)
-install_github("philipdelff/NMdata")
+install_github("nmautoverse/NMdata")
library(NMdata)
-If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
+If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
Issues?
-The best way to report a bug or to request features is on github.
+The best way to report a bug or to request features is on github.
Code of Conduct
-Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
+Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
@@ -295,8 +296,8 @@ Developers
Dev status
diff --git a/pkgdown.yml b/pkgdown.yml
index 59acfb8e..7b50c614 100644
--- a/pkgdown.yml
+++ b/pkgdown.yml
@@ -7,7 +7,7 @@ articles:
NMdata-FAQ: NMdata-FAQ.html
NMscanData: NMscanData.html
ParameterTables: ParameterTables.html
-last_built: 2024-10-30T13:46Z
+last_built: 2024-10-30T14:58Z
urls:
reference: https://nmautoverse.github.io/NMdata/reference
article: https://nmautoverse.github.io/NMdata/articles
diff --git a/reference/NMdataConf.html b/reference/NMdataConf.html
index 04e7d9d4..9f57de6b 100644
--- a/reference/NMdataConf.html
+++ b/reference/NMdataConf.html
@@ -273,7 +273,7 @@ Examples
#> return(as.data.frame(list()))
#> UseMethod("as.data.frame")
#> }
-#> <bytecode: 0x555b11fa7578>
+#> <bytecode: 0x5589109e5260>
#> <environment: namespace:base>
#>
#> $check.time
@@ -311,32 +311,32 @@ Examples
#> {
#> fnExtension(file, ext = ".ext")
#> }
-#> <bytecode: 0x555b1223c698>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x5589109ffeb0>
+#> <environment: 0x5589109e4930>
#>
#> $file.cov
#> function (file)
#> {
#> fnExtension(file, ext = ".cov")
#> }
-#> <bytecode: 0x555b1223bfd0>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x5589109ff7e8>
+#> <environment: 0x5589109e4930>
#>
#> $file.phi
#> function (file)
#> {
#> fnExtension(file, ext = ".phi")
#> }
-#> <bytecode: 0x555b120ce868>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a02f50>
+#> <environment: 0x5589109e4930>
#>
#> $file.shk
#> function (file)
#> {
#> fnExtension(file, ext = ".shk")
#> }
-#> <bytecode: 0x555b120ce1a0>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a02888>
+#> <environment: 0x5589109e4930>
#>
#> $file.mod
#> function (file)
@@ -350,8 +350,8 @@ Examples
#> }
#> ctl
#> }
-#> <bytecode: 0x555b120cdad8>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a021c0>
+#> <environment: 0x5589109e4930>
#>
#> $file.data
#> [1] "extract"
@@ -362,8 +362,8 @@ Examples
#> $modelname
#> function (file)
#> fnExtension(basename(file), "")
-#> <bytecode: 0x555b120d0a98>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a070a0>
+#> <environment: 0x5589109e4930>
#>
#> $nc
#> [1] 64
diff --git a/reference/NMstamp.html b/reference/NMstamp.html
index 6bd1eb18..249636a1 100644
--- a/reference/NMstamp.html
+++ b/reference/NMstamp.html
@@ -145,7 +145,7 @@ Examples
#> [1] "example.R"
#>
#> $dataCreate$CreationTime
-#> [1] "2024-10-30 13:46:31 UTC"
+#> [1] "2024-10-30 14:58:28 UTC"
#>
#> $dataCreate$description
#> [1] "Example data"
Traceability#> [1] "NMdata-cheat.Rmd"
#>
#> $CreationTime
-#> [1] "2024-10-30 13:46:44.829605"
+#> [1] "2024-10-30 14:58:42.555296"
#>
#> $writtenTo
#> [1] "derived/pkdata.rds derived/pkdata.csv"
diff --git a/index.html b/index.html
index 2ab39f18..eceb60c4 100644
--- a/index.html
+++ b/index.html
@@ -107,7 +107,7 @@
-NMdata
+
@@ -129,24 +129,25 @@ NMdata is not a silo
More information
-The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
+The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
-
-
+
+
How to install
NMdata is on CRAN and MPN. To install from the package archive you are already using, do:
-
+
+install.packages("NMdata")
+library(NMdata)
See further below for instructions on how to install from other sources than your default archive, if need be.
Prepare, check, and export PK/PD data
-On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
+On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
Check data as read by NONMEM
@@ -195,7 +196,7 @@ Automated and gener
NMdataConf(as.fun="data.table")
res.dt <- NMscanData("xgxr001.lst",quiet=TRUE)
-
NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
+NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
Meta analysis made really easy
@@ -216,7 +217,7 @@ Meta analysis made really easy#> Warning: Transformation introduced infinite values in continuous y-axis
#> Warning: Transformation introduced infinite values in continuous y-axis
-
+
Get the most recent version
@@ -228,24 +229,24 @@ Get the most recent version
## Option 3: Install from github
library(remotes)
-install_github("philipdelff/NMdata")
+install_github("nmautoverse/NMdata")
library(NMdata)
-If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
+If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
Issues?
-The best way to report a bug or to request features is on github.
+The best way to report a bug or to request features is on github.
Code of Conduct
-Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
+Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
@@ -295,8 +296,8 @@ Developers
Dev status
diff --git a/pkgdown.yml b/pkgdown.yml
index 59acfb8e..7b50c614 100644
--- a/pkgdown.yml
+++ b/pkgdown.yml
@@ -7,7 +7,7 @@ articles:
NMdata-FAQ: NMdata-FAQ.html
NMscanData: NMscanData.html
ParameterTables: ParameterTables.html
-last_built: 2024-10-30T13:46Z
+last_built: 2024-10-30T14:58Z
urls:
reference: https://nmautoverse.github.io/NMdata/reference
article: https://nmautoverse.github.io/NMdata/articles
diff --git a/reference/NMdataConf.html b/reference/NMdataConf.html
index 04e7d9d4..9f57de6b 100644
--- a/reference/NMdataConf.html
+++ b/reference/NMdataConf.html
@@ -273,7 +273,7 @@ Examples
#> return(as.data.frame(list()))
#> UseMethod("as.data.frame")
#> }
-#> <bytecode: 0x555b11fa7578>
+#> <bytecode: 0x5589109e5260>
#> <environment: namespace:base>
#>
#> $check.time
@@ -311,32 +311,32 @@ Examples
#> {
#> fnExtension(file, ext = ".ext")
#> }
-#> <bytecode: 0x555b1223c698>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x5589109ffeb0>
+#> <environment: 0x5589109e4930>
#>
#> $file.cov
#> function (file)
#> {
#> fnExtension(file, ext = ".cov")
#> }
-#> <bytecode: 0x555b1223bfd0>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x5589109ff7e8>
+#> <environment: 0x5589109e4930>
#>
#> $file.phi
#> function (file)
#> {
#> fnExtension(file, ext = ".phi")
#> }
-#> <bytecode: 0x555b120ce868>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a02f50>
+#> <environment: 0x5589109e4930>
#>
#> $file.shk
#> function (file)
#> {
#> fnExtension(file, ext = ".shk")
#> }
-#> <bytecode: 0x555b120ce1a0>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a02888>
+#> <environment: 0x5589109e4930>
#>
#> $file.mod
#> function (file)
@@ -350,8 +350,8 @@ Examples
#> }
#> ctl
#> }
-#> <bytecode: 0x555b120cdad8>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a021c0>
+#> <environment: 0x5589109e4930>
#>
#> $file.data
#> [1] "extract"
@@ -362,8 +362,8 @@ Examples
#> $modelname
#> function (file)
#> fnExtension(basename(file), "")
-#> <bytecode: 0x555b120d0a98>
-#> <environment: 0x555b11fa6c48>
+#> <bytecode: 0x558910a070a0>
+#> <environment: 0x5589109e4930>
#>
#> $nc
#> [1] 64
diff --git a/reference/NMstamp.html b/reference/NMstamp.html
index 6bd1eb18..249636a1 100644
--- a/reference/NMstamp.html
+++ b/reference/NMstamp.html
@@ -145,7 +145,7 @@ Examples
#> [1] "example.R"
#>
#> $dataCreate$CreationTime
-#> [1] "2024-10-30 13:46:31 UTC"
+#> [1] "2024-10-30 14:58:28 UTC"
#>
#> $dataCreate$description
#> [1] "Example data"
NMdata
+
@@ -129,24 +129,25 @@ NMdata is not a silo
More information
-The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
+The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
-
-
+
+
More information
-The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
+The best place to browse information about the package is here. The quickest way in is the Cheatsheet.
- -
How to install
NMdata is on CRAN and MPN. To install from the package archive you are already using, do:
+install.packages("NMdata")
+library(NMdata)See further below for instructions on how to install from other sources than your default archive, if need be.
Prepare, check, and export PK/PD data
-On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
+On the data-generation side, functionality is provided for documentation of the datasets while generating them. Check out this vignette on the topic. There are functions for automatic checks of (some) data merges, handling and counting of exclusions flags, final preparations for ensuring readability in NONMEM, and ensuring traceability of datasets back to data generation scripts.
Check data as read by NONMEM
@@ -195,7 +196,7 @@ Automated and gener
NMdataConf(as.fun="data.table")
res.dt <- NMscanData("xgxr001.lst",quiet=TRUE)
-
NMdataConf(as.fun="data.table")
res.dt <- NMscanData("xgxr001.lst",quiet=TRUE)NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
NMscanData is very general, and should work with all kinds of models, and all kinds of other software and configurations. Take a look at this vignette for more info on the NONMEM data reader. Then you will learn how to access the meta data that will allow you to trace every step that was taken combining the data and the many checks that were done along the way too.
Meta analysis made really easy
@@ -216,7 +217,7 @@ Meta analysis made really easy#> Warning: Transformation introduced infinite values in continuous y-axis
#> Warning: Transformation introduced infinite values in continuous y-axis
Get the most recent version
@@ -228,24 +229,24 @@ Get the most recent version
## Option 3: Install from github
library(remotes)
-install_github("philipdelff/NMdata")
+install_github("nmautoverse/NMdata")
library(NMdata)
If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
+If you use the Github version, you may want to see the FAQ for how to install specific releases from Github (ensuring reproducibility).
Issues?
-The best way to report a bug or to request features is on github.
+The best way to report a bug or to request features is on github.
Code of Conduct
-Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
+Please note that the patchwork project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.