Repository navigation
Split analysis/ by dataset, then by topic - #17
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 052459ee89
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Humans work in notebooks, flat under `analysis/<topic>/`, writing to `data/<dataset>/results/` and | ||
| `figures/<topic>/`; notebook outputs are committed. Agents work in task directories, with scripts. | ||
| `analysis/` is split by dataset, then by broad topic: `analysis/<dataset>/<topic>/`, with the dataset level even when |
There was a problem hiding this comment.
When a task consumes another task's output under this newly required dataset/topic hierarchy, the copied template still instructs authors at skills/analysis-workflow/assets/task_template/README.md:26 to record analysis/<other_task>/outputs/<file>. That omits the dataset and topic components, so following the template produces a non-existent input path and makes the task README's rerun instructions incorrect; update the template example to include both levels.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in f878e0d: the example is now analysis/<dataset>/<topic>/<other_task>/outputs/<file>. It was the only remaining path without both levels.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 participant
analysis/is now split by dataset, then by broad topic:analysis/<dataset>/<topic>/, with the dataset level even in a repo with one dataset. Topics such aspreprocessing/,annotation/orspatial/can mostly be worked on in any order. Notebooks sit flat under a topic and write figures tofigures/<dataset>/<topic>/; task directories sit under a topic too.The skill's "Two lanes" states the layout; the session-start rule, the README and the layout guard's docstring show the new task path. The guard itself is unchanged: it only requires a task directory's name to end in
_vN. Version 0.5.0.The analysis template's review guide and
.gitignorecomment follow in quadbio/analysis_template.🤖 Generated with Claude Code