Skip to content

get_german_credit_risk_dataset.sas runs unmodified on Jenner - #1

Open
jenner-analytics wants to merge 1 commit into
Bayunova28:masterfrom
jenner-analytics:jenner-check/initial-bundles
Open

get_german_credit_risk_dataset.sas runs unmodified on Jenner#1
jenner-analytics wants to merge 1 commit into
Bayunova28:masterfrom
jenner-analytics:jenner-check/initial-bundles

Conversation

@jenner-analytics

Copy link
Copy Markdown

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 get_german_credit_risk_dataset.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 project, shared in case it's useful, and was assembled with AI assistance as is most code in modern businesses today.

You consistently used SAS name literals ('Saving accounts'n, 'Credit amount'n) under VALIDVARNAME=ANY to keep the dataset's original spaced column names intact end-to-end, through the PROC SQL aggregations, the SGPLOT calls, and the missing-value recode (if 'Saving accounts'n='NA' then 'Saving accounts'n='Unknown') — rather than the more common shortcut of renaming everything to underscores up front. It's a small choice, but it keeps the code closer to the original UCI column labels the whole way through.

jenner-check/ in this PR holds three bundles built from your two batch scripts (the CAS-based Bayesian network scorer needs a live Viya grid, so it's out of scope for a hosted-API bundle): the import/describe step, the PROC MEANS + PROC SGPLOT + PROC SQL exploratory slice, and the savings-accounts recode + PROC GCHART slice.

jenner-check/
├── README.md
├── run_jenner.sh
├── t001_get_dataset/            # PROC IMPORT-style load, PROC PRINT, PROC CONTENTS
├── t002_explore_dataset/        # PROC SQL, PROC MEANS, PROC SGPLOT
└── t003_savings_by_amount/      # missing-value recode, PROC GCHART

Check out this PR's branch and run from the repo root to try one directly:

gh pr checkout 1
curl -sS --data-binary @jenner-check/t001_get_dataset/script.sas https://api.jenneranalytics.com/v1/quick

cd jenner-check && ./run_jenner.sh --all re-runs all three and checks each result against its pinned expected.json. The hosted API is free to try, no signup — full API reference: the docs.

The runner uploads 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 doesn't read or upload your CSV or any other data file — only the code you run is transmitted, as with pasting a snippet into any hosted tool — and nothing is sent unless you run a command yourself.

Merge, close, or ignore this PR — no response expected, and we won't open further PRs in this repo. To opt out for good, mention no-more-prs in any comment, or open an issue titled jenner-check: opt out.


Lawrence W. Sinclair
CEO / Jenner Analytics Ltd
linkedin.com/in/lwsinclair/

Adds jenner-check/ with three self-contained bundles built from this
repo's SAS scripts (import/describe, PROC SQL + PROC MEANS + PROC
SGPLOT exploratory slice, and a missing-value recode + PROC GCHART
slice), each pinned against a captured passing run from
api.jenneranalytics.com, plus the runner script and its README.
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