Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ux: re-consider user experience when running multiple configurations against same inputs #261

Open
jdhoffa opened this issue Nov 22, 2024 · 1 comment

Comments

@jdhoffa
Copy link
Member

jdhoffa commented Nov 22, 2024

          > I still feel some tension about the config that I can't quite explain. I guess our cookbook suggests that one might/should run parts of the process multiple times with tweaked settings, which implies to me that they may be using multiple config files and have multiple roughly equivalent sub directories, e.g. `analyse_by_group` and `analyse_by_sector`. And we even facilitated using full paths to each directory, so those sub directories don't even need to be in the same project directory (iirc we specifically thought that the `input` directory might likely be in a separate location).

I don't have a good suggestion here (sorry), just being forward about a bit of hesitation I have.

Originally posted by @cjyetman in #258 (comment)

@jdhoffa jdhoffa self-assigned this Nov 22, 2024
@jdhoffa jdhoffa changed the title re-consider user experience when running multiple configurations against same inputs ux: re-consider user experience when running multiple configurations against same inputs Nov 22, 2024
@jdhoffa
Copy link
Member Author

jdhoffa commented Dec 9, 2024

When one fininshes a run, and then wants to go back and run another analysis:

  • I will need to go back and change the config.yml values
  • I will also need to change the directory names

Maybe we can make it more clear that if you want to adjust the configuration, you also need to update the output directory names so that you don't overwrite data.

@jdhoffa jdhoffa removed their assignment Dec 9, 2024
@jdhoffa jdhoffa removed the priority label Dec 9, 2024
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

No branches or pull requests

1 participant