Repository navigation
Conversation
* Read the saved results of the analyses in a JASP file readAnalysisResultsFromJaspFile() gives, per analysis of a .jasp file, the results JASP Desktop saved in analyses.json (decoded, raw cell values), with its id, name, title, module, module version and status; the JASP and archive versions of the file are attributes. This is the reference a re-run of the analyses can be compared with. The module/version lookup and the reading of a JSON entry of the archive are shared with readAnalysisOptionsFromJaspFile(); the entry is read as UTF-8. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Version 1.4.2: readAnalysisResultsFromJaspFile Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * readAnalysisResultsFromJaspFile docs: no encoded-name grammar in the R sources test-no-regex-token-decoding forbids the legacy token pattern in R/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…columns (jasp-stats#25) The bridge gives nominal columns as factors and ordinal columns as ordered factors, with their levels in the order of the file, but readDatasetFromJaspFile turned them into character vectors. Loaded again with loadDataSet(), their levels were then ordered alphabetically: in puppies.jasp (jaspAnova) Dose became "15 mins", "30 mins", "No puppies" instead of "No puppies", "15 mins", "30 mins", so its simple and custom contrasts compared other levels than in JASP. The factors are now kept, and loadDataSet() keeps their level order (jasp-stats#19). Version 1.4.3 (after 1.4.2 of readAnalysisResultsFromJaspFile). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
parseQmlOptions (also behind readAnalysisOptionsFromQml and jaspTools'
analysisOptions) used the native parse for runs, which requires every dataset
selection option of a multi-dataset form to name a loaded dataset: the defaults of
such a form could not be read at all. It now uses the new native
syntaxBridgeLoadQmlAndParseFormOptionsStatus (jasp-desktop): a dataset selection
that names no dataset stays empty (""), and no multi-dataset run is prepared. A
selection that is given must still name a loaded dataset. Runs
(loadQmlAndParseOptions(Status), used by jaspBase) are unchanged.
Needs a SyntaxInterface release with that export. Version 1.4.5.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 16, 2026
Run the analyses of a .jasp file again through jaspSyntax and the R wrapper
jasp-stats/jaspTools#101
Open
Closed
flattenTypes (jasp-stats#20) was added for jaspTools' analysisOptions(<file>.jasp), which split the saved {value, types} options into <name> and <name>.types. jaspTools now gives the saved options as they are: the QML form of the analysis reads that shape, and it runs an analysis of a .jasp file through jaspBase::runWrappedAnalysis. Nothing else used it, so the argument and the internal flattenedAnalysisOptionsFromJaspFile go. The nested <name>.types that the option encoder writes are still dropped with includeTypeOptions = FALSE, for the runtime options. Version 1.4.4. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
parseQmlOptions()(also behindreadAnalysisOptionsFromQml()and jaspTools'analysisOptions()) used the native parse for runs. That parse requires every dataset selection option of a multi-dataset form to name a loaded dataset, so the defaults of such a form could not be read at all, with or without datasets loaded.Change
parseQmlOptions()now calls the new nativeloadQmlAndParseFormOptions()→syntaxBridgeLoadQmlAndParseFormOptionsStatus(jasp-stats/jasp-desktop#6414):""), whatever is loaded;parseQmlOptions()never prepares a run anyway: runs go throughloadQmlAndParseOptions(Status)(jaspBase), which is unchanged and still refuses an empty selection.Two tests in
test-selection-surface.R: the defaults without a dataset, and with datasets loaded (empty stays empty, a given selection resolves, an unknown one fails, a run still needs one).Version 1.4.5 (follows #24, #25 and #26; the version line may conflict trivially).
Merge order
This needs a SyntaxInterface release with the new export: it cannot build against v1.0.beta.8. Merge after jasp-stats/jasp-desktop#6414 is in a release, and bump the release tag in
configure/configure.winthen.Tests
Against a SyntaxInterface built from #6414: 524 expectations, 0 failures (the 2
test-dataset-info.Rfailures seen with beta.8 pass too, as this library is newer). jaspTools'analysisOptions("multiDataSetFunc")+runAnalysis()with two datasets now runs, with the same results as with hand-built options; jaspTools has a test for it (jasp-stats/jaspTools#101), skipped below jaspSyntax 1.4.5.🤖 Generated with Claude Code