Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include LOG10 in nm-vars #1173

Open
kylebaron opened this issue Feb 20, 2024 · 3 comments
Open

Include LOG10 in nm-vars #1173

kylebaron opened this issue Feb 20, 2024 · 3 comments

Comments

@kylebaron
Copy link
Collaborator

kylebaron commented Feb 20, 2024

Right now, we only have LOG, not LOG10

@mattfidler
Copy link

In case you need a list of supported functions for nm-vars there is one in the nonmem2rx parser syntax:

https://github.com/nlmixr2/nonmem2rx/blob/d74a4eef3a9c0211636cd0931f8424a2bd64e195/inst/abbrev.g#L233

I think I captured them all, but am unsure.

@kylebaron
Copy link
Collaborator Author

Thanks for sharing this, @mattfidler; very helpful. I'd like to find a way to tap into what you're doing with the nonmem parser some day; much more elegant than what I'm doing for now.

Kyle

@mattfidler
Copy link

No problem Kyle, thought the function names might be helpful (it took me a bit to find from the NONMEM manual).

As far as the NONMEM translator, it translates directly to rxode2, so it may not be as useful for mrgsolve directly (unless we eventually figure out some translator, which is still on my internal backlog).

However, the nonmem2rx::nminfo() may be useful for reading NONMEM by itself. If I recall correctly you guys already have some of these utilities yourself (so it may not be useful).

However, if you decide to translate monolix, the monolix2rx parses most of the content to R first, so that may be useful if you want to include a translator from that direction (which I think is likely a long term project for you guys).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants