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

[FEATURE REQUEST] Store GCC vs GCC plots in BenchmarkResults/GCC_version_comparison #171

Open
yantosca opened this issue Oct 4, 2022 · 1 comment
Assignees
Labels
category: Feature Request New feature or request topic: Benchmark Plots and Tables Issues pertaining to generating plots/tables from benchmark output

Comments

@yantosca
Copy link
Contributor

yantosca commented Oct 4, 2022

The script gcpy/benchmark/run_benchmark.py currently places GCC vs. GCC plots in the BenchmarkResults folder (or whatever name gcc_vs_gcc_resultsdir specifies). However, GCHP vs GCC plots are created in BenchmarkResults/GCHP_vs_GCC_comparison and GCHP vs. GCHP plots are created in BenchmarkResults/GCHP_version_comparison.

For consistency, could we make run_benchmark.py create a BenchmarkResults/GCC_version_comparison folder? This would be consistent usage with the 1-year benchmarks.

NOTE: I didn't implement this myself because I didn't want to break the cloud benchmarks.

@yantosca yantosca added category: Feature Request New feature or request topic: Benchmark Plots and Tables Issues pertaining to generating plots/tables from benchmark output labels Oct 4, 2022
@yantosca yantosca added this to the 1.3.0 milestone Oct 4, 2022
@msulprizio msulprizio modified the milestones: 1.3.0, 1.4.0 Dec 22, 2022
@yantosca yantosca modified the milestone: 1.4.0 Nov 20, 2023
Copy link

Stale issue message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Feature Request New feature or request topic: Benchmark Plots and Tables Issues pertaining to generating plots/tables from benchmark output
Projects
None yet
Development

No branches or pull requests

3 participants