The choice of where GuPPy writes its pipeline outputs currently lives inside the Storenames GUI, behind a menu button labeled over-write storeslist file or create a new one?. Two unrelated decisions are coupled in one panel: "what are my channel names?" and "where does the entire pipeline write its outputs?". This pairing is confusing for me as a first time user when I was working on. PR #303. As a testament of this, the proposed tutorial there spends two of its six Storenames substeps and an admonition box explaining what the menu does and how the over_write_file option destructively wipes prior results.
I think this should live on the homepage instead. We can have it right at the beginning so the user selects a folder where everything will be stored. This will make the choice clear, separated, and global, while letting the Storenames panel reduce to the single job it is named for.
The choice of where GuPPy writes its pipeline outputs currently lives inside the Storenames GUI, behind a menu button labeled
over-write storeslist file or create a new one?. Two unrelated decisions are coupled in one panel: "what are my channel names?" and "where does the entire pipeline write its outputs?". This pairing is confusing for me as a first time user when I was working on. PR #303. As a testament of this, the proposed tutorial there spends two of its six Storenames substeps and an admonition box explaining what the menu does and how theover_write_fileoption destructively wipes prior results.I think this should live on the homepage instead. We can have it right at the beginning so the user selects a folder where everything will be stored. This will make the choice clear, separated, and global, while letting the Storenames panel reduce to the single job it is named for.