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

Sim casal2 202206 #394

Merged
merged 3 commits into from
Jun 28, 2022
Merged

Sim casal2 202206 #394

merged 3 commits into from
Jun 28, 2022

Conversation

Craig44
Copy link
Contributor

@Craig44 Craig44 commented Jun 28, 2022

  • Please check that the PR fulfills these requirements
  • The commit message follows the Contributor Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Documents have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • What is the current behavior? (You can also link to an open issue here)

  • What is the new behavior (if this is a feature change)?

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

  • Other information:

Craig44 added 3 commits June 28, 2022 20:42
…n label supplied will print all of them

add a test model to test this new simulated report
I am going to try do it through R. Will be easier to manipulate R files.
@Craig44
Copy link
Contributor Author

Craig44 commented Jun 28, 2022

I experimented with re-enacting simCASAL utility code but was quite difficult due to the file structures of a model. I have decided to take the R approach when conducting the self test re #393

@Craig44 Craig44 merged commit 85ba18d into master Jun 28, 2022
@Casal2 Casal2 deleted the simCASAL2_202206 branch June 26, 2024 04:13
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

Successfully merging this pull request may close these issues.

1 participant