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

Make language development screening available to JAMES #4

Open
7 tasks
stefvanbuuren opened this issue Oct 18, 2023 · 0 comments
Open
7 tasks

Make language development screening available to JAMES #4

stefvanbuuren opened this issue Oct 18, 2023 · 0 comments

Comments

@stefvanbuuren
Copy link
Member

growthscreener 1.20.0.9000 extends the list_screeners() function to include 4000-codes for language development. Making the screener available to JAMES still requires a few steps:

  • Extend bdsreader::read_bds() to save Van Wiechen items 41-46 by default to JAMES internal format. There is already a switch append_ddi, but that should be refined to filter only items 41-46;
  • Create growthscreener::calculate_advice_lgd() that implements the functionality of calculate_advice_devlang(), but using the default gsed 9-position naming schema and the long format used in the xyz component created by read_bds(). Perhaps calculate_advice_lgd() could wrap calculate_advice_devlang();
  • Test that calculate_advice_lgd() and calculate_advice_devlang() do the same from different argument specifications;
  • Extend argument yname in growthscreener::screen_curves_tgt() to include the lgd (language development) code;
  • Extend growthscreener::screen_curves_tgt() with a call to calculate_advice_lgd();
  • Add test for growthscreener::screen_curves_tgt();
  • Update NEWS and version in JAMES.
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

1 participant