Skip to content

Performance and trendy updates#172

Open
StevenM1 wants to merge 35 commits into
devfrom
oo_refactor_simd
Open

Performance and trendy updates#172
StevenM1 wants to merge 35 commits into
devfrom
oo_refactor_simd

Conversation

@StevenM1
Copy link
Copy Markdown
Collaborator

The big one. Includes:

A couple of important things to be aware of:

  • By default, it longer relies on R's pnorm, but instead uses Hart's approximation (~double precision). can be reverted back to original R's pnorm with a compile-time flag. See pnorm_utils.h.

  • For macOS, makes use of the Accelerate platform to speed up some transformations (exp and log). This requires a configuration instead of just Makevars (which don't allow for running arbitrary bash code, which is needed to detect the platform). configure is basically a .sh script that generates Makevars. The defaults should be CRAN-safe. For optimal performance, use remotes::install_github('ampl-psych/EMC2@dev, configure.args=c('--native'))

@StevenM1
Copy link
Copy Markdown
Collaborator Author

Arghh - something broke, sorry, I thought check passed but it didn't...

StevenM1 added 6 commits May 20, 2026 16:34
…Allows for keeping track of which columns are design columns and which are parameter names. Also allows for more robust checking of duplicate parameter names.
@StevenM1
Copy link
Copy Markdown
Collaborator Author

Alright, fixed. @niekstevenson do you want to press the magic button?

@niekstevenson
Copy link
Copy Markdown
Collaborator

Hey I can press the magic button, but it seems like you're still making commits? It's looking very clean as always! Just let me know when you're ready

@StevenM1
Copy link
Copy Markdown
Collaborator Author

Yes - again, not sure what the best way of working here is :-) Reason I'm still making commits is that I am working on one of the tutorials, for which I need this code. The commits pertain things not really related to the big merge itself - e.g., minor plotting changes, etc.
So once merged, for such things in the future, I'd like to see if I can push those directly in dev? Or I just keep working on a separate branch, and we occasionally (eg during our biweekly meeting?) merge them again (+detect and fix conflicts at that stage), to prevent major diverging code?

@niekstevenson
Copy link
Copy Markdown
Collaborator

Sounds good! For now I will merge this into dev and you can branch of that again?

@StevenM1
Copy link
Copy Markdown
Collaborator Author

StevenM1 commented May 22, 2026 via email

@StevenM1 StevenM1 force-pushed the oo_refactor_simd branch 4 times, most recently from bef2af3 to 48924ff Compare May 23, 2026 12:02
…mfcol. By default setting par() with mfcol/mfrow overwrites the cex setting, which limits user control over label sizes
@StevenM1 StevenM1 force-pushed the oo_refactor_simd branch from 48924ff to 8bd4038 Compare May 23, 2026 15:25
@StevenM1 StevenM1 force-pushed the oo_refactor_simd branch 2 times, most recently from 811e095 to 91a4fcb Compare May 29, 2026 08:42
… overlaying ground-truth (data-generating) trajectory/ies
@StevenM1 StevenM1 force-pushed the oo_refactor_simd branch from 91a4fcb to 6288de4 Compare June 1, 2026 14:00
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.

2 participants