Skip to content

Add USRSE 2026 STAMPED poster abstract - #14

Draft
leej3 wants to merge 2 commits into
masterfrom
agent/usrse-stamped-poster
Draft

Add USRSE 2026 STAMPED poster abstract#14
leej3 wants to merge 2 commits into
masterfrom
agent/usrse-stamped-poster

Conversation

@leej3

@leej3 leej3 commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

Add poster abstract. Addresses con/cierge#34

Validation

  • abstract: 463 words and visually verified to fit entirely on page 1
  • US-RSE connection statement: 237 words, below the 300-word limit
  • generated submission PDF: 2 pages, with supporting material beginning on page 2
  • Markdown source checked with git diff --check

The generated PDF remains a local submission artifact because 2026-usrse/.gitignore excludes PDFs, matching the repository’s existing USRSE poster-draft convention.

Co-Authored-By: codex-cli 0.143.0 / gpt 5.6-luna <codex@openai.com>

@asmacdo asmacdo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Handful of nitpicks, take what you like.

Comment thread 2026-usrse/stamped-abcd-poster-draft.md Outdated
Comment thread 2026-usrse/stamped-abcd-poster-draft.md Outdated

- **Self-contained:** Everything needed to understand and run the study was made identifiable from one research-object boundary, reducing reliance on undocumented local context (supported by DataLad and git-annex).
- **Tracked:** Results were linked to their inputs, transformations, execution context, and scientific meaning so their provenance could be inspected (recorded with Git, DataLad run records, `con-duct`, and NIDM/PROV).
- **Actionable:** Procedures and expected outputs were encoded as executable, testable operations instead of instructions requiring interpretation (implemented through BIDS, tested BIDS Apps, Pixi tasks, manifests, and validation commands).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

datalad rerun might be useful here too, though the list is already pretty long.

Comment thread 2026-usrse/stamped-abcd-poster-draft.md Outdated
- **Self-contained:** Everything needed to understand and run the study was made identifiable from one research-object boundary, reducing reliance on undocumented local context (supported by DataLad and git-annex).
- **Tracked:** Results were linked to their inputs, transformations, execution context, and scientific meaning so their provenance could be inspected (recorded with Git, DataLad run records, `con-duct`, and NIDM/PROV).
- **Actionable:** Procedures and expected outputs were encoded as executable, testable operations instead of instructions requiring interpretation (implemented through BIDS, tested BIDS Apps, Pixi tasks, manifests, and validation commands).
- **Modular:** Data, environments, operations, and results retained distinct identities so components could be reviewed, updated, and reused independently (organized as versioned DataLad components).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Modular:** Data, environments, operations, and results retained distinct identities so components could be reviewed, updated, and reused independently (organized as versioned DataLad components).
- **Modular:** Data, environments, operations, and results retained distinct identities so components could be reviewed, updated, and reused independently (organized as versioned DataLad subdatasets).

I read this as a datalad component being a "thing".

Comment thread 2026-usrse/stamped-abcd-poster-draft.md Outdated

The scientific value of a computational finding depends on whether others can understand how it was produced, inspect its evidence, and repeat or extend the analysis. Code alone does not provide this: data, parameters, software environments, execution context, and the provenance connecting inputs to outputs must also be identifiable and recoverable. STAMPED defines seven properties for organizing these materials as a durable research object.

We applied STAMPED to reproduce an analysis presented at OHBM 2025 on age-dependent bias in cortical morphometry tools using Adolescent Brain Cognitive Development (ABCD) Study data. This case study shows how the principles translate into concrete research-design choices and how those choices make a computational result easier to inspect, execute, verify, and reuse.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be good to mention AI in the first couple paragraphs, the final paragraph makes the connection to AI feel bolted on. I suppose the strongest place to mention would be to discuss how AI played a role in your application of STAMPED here.

Co-Authored-By: codex-cli 0.143.0 / gpt 5.6-sol <codex@openai.com>
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