cogvars_gdr_20251107.sas runs unmodified on Jenner — test bundle#2
Open
jenner-analytics wants to merge 1 commit into
Open
Conversation
Adds a self-contained jenner-check/ directory with three compatibility bundles derived from this repo's SAS: - t001_merge2sets: the %merge2sets sort/keep/merge utility - t002_proxy_iqcode: the %proxy Jorm IQCODE derivation - t003_frailtyscore: the frailty-score domain + 0-4 scoring data step Each bundle carries a copy of the construct, a small mock input, the captured log and listing from a passing run on Jenner, and a shell runner. Nothing outside jenner-check/ is touched and nothing executes on merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jenneranalytics.com provides an API that runs SAS code, with support for more than 200 SAS procedures. You can also use it with AI assistants in a collaborative workspace. It's available for Mac on the Apple App Store, and by license for Windows and Linux.
We support the larger community by
(1) increasing access to SAS-compatible systems,
(2) by providing test coverage and a test coverage framework to public SAS repos in order to encourage the use of best practices in software engineering.
Your cogvars_gdr_20251107.sas runs on Jenner unmodified — this PR adds a small compatibility bundle so you can see for yourself. It's the test we wrote for your library, shared in case it's useful, and was assembled with AI assistance as is most code in modern businesses today.
Reading through the cognitive-measures program, the piece that stood out is the
%proxymacro's handling of the Jorm IQCODE. Rather than dropping "other / don't know / refused" item responses, it folds them toward the nearest unchanged category — a7/8/9on the improved branch becomes "a bit improved" and on the declined branch "a bit worse" — so a proxy interview with a few unusable items still contributes a sixteen-item average instead of going missing entirely. The%merge2setsutility is a nice companion: one place for the sort/keep/merge boilerplate that the rest of the pipeline leans on, instead of that pattern being re-typed at every join. Documented decisions like these are what make derivation code trustworthy to reuse, and they're the parts worth pinning a test around.The bundle lives entirely under
jenner-check/— three self-contained tests, each a copy of one of your constructs plus a small mock input, the captured log and listing from a passing run, and a runner. Nothing outsidejenner-check/is touched, nothing runs on merge, and there are no workflow files or hooks.To try one against the hosted engine, check out this PR and run from the repo root:
# puts you on this PR's branch, then run from the repo root: gh pr checkout 2 curl -sS --data-binary @jenner-check/t001_merge2sets/script.sas https://api.jenneranalytics.com/v1/quickOr
cd jenner-check && ./run_jenner.sh --all, which re-runs every bundle and checks the pinned fields in eachexpected.json. The API is free to try with no signup; full API reference: the docs.On data: the runner sends only the SAS source text of the script it runs (plus a two-line autoexec) to api.jenneranalytics.com, which runs it and returns the log and listing. It does not read or upload any data files — each bundle carries its own small mock input in the columns the construct reads — so anything sitting next to a script stays on your machine, and nothing is transmitted unless you run one of these commands yourself. As with pasting a snippet into any hosted tool, only the code you run is transmitted, so you can review a script first if it ever embeds sensitive values inline.
Merge it, close it, or ignore it — all fine, and no response is expected. We won't open further PRs in this repo. To opt out of any future contact, leave
no-more-prsin a comment or open an issue titledjenner-check: opt out.Lawrence W. Sinclair
CEO / Jenner Analytics Ltd
linkedin.com/in/lwsinclair/