-
Notifications
You must be signed in to change notification settings - Fork 13
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
RXR-1751 add safety #78
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes seems ok but I don't understand the reason behind removing the .Rproj file? Granted I don't use it since I don't use RStudio, but I thought most people do?
We can discuss, but IMO .Rproj files shouldn't be included, I sere it as more of a user/environment specific file rather than something specific to the package. In this case it was annoying because it stores a flag that controls compilation (if all C++ source files should be recompiled. The current version has that flag set to true, but it takes 30 secs or so extra so annoying when developing). I could've set it to false but decided to remove instead. |
I think we should at least briefly discuss with the team to avoid breaking anyone's workflow for working with RStudio projects, because after this change RStudio's various project-specific options won't work (i.e. "open project" and "recent projects" won't work, you won't be able to double click on the .Rproj files to launch an RStudio session in that project, etc.). Can we make it a separate PR from the RXR-1751 change? |
Sounds good. I mean the idea is still that everyone (that uses RStudio) keeps the Rproj file, just not committed to git. We'll discuss tomorrow. |
@@ -17,5 +17,6 @@ StripTrailingWhitespace: Yes | |||
|
|||
BuildType: Package | |||
PackageUseDevtools: Yes | |||
PackageCleanBeforeInstall: No |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the setting I mentioned. For PKPDsim it's better if this is set to no
, since we don't want to keep compiling the C++ code
When duplicate names are used in
covariate
anddeclare_variables
arguments, the covariates are not exported in the output column. Example to see this:After this change it's now impossible to specify duplicate covariates and variables in model specs. I initially implemented code in
sim()
that checks for duplicates in the output of sim() and made the parsing safer, but I removed that because it should now be unnecessary.