MetOffice / MetOffice/Vernier

[Custom Issue]: Differencing two sets of output.

Open
#246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
6
Forks
11
Avg merge
18h 7m
Merged PRs (30d)
1

Description

### Contact Details

_No response_

### Are there any linked Issues or Pull Requests?

_No response_

### Brief description

It'd be useful to support a command-line tool which takes two sets of Vernier output and orders the profiled regions according to differences in timings. e.g. `vernier-diff /path/to/runA /path/to/runB`. If particular regions took longer in runB, then their timings would be -ve and appear at the top of the list.

```
Baseline file: baseline-file.out, procs: 0001, threads: 01
Test file: test-file.out, procs: 0001, threads: 01

Rank Routine name Time difference (s)
------- ------------------------------------------------------- -------------------
1 some_subroutine -20.565
2 another_subroutine -16.593
3 my_function -11.353
4 another_function 2.450
```

### Further details of the issue.

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or existing entry points are named. Start by locating Vernier's command-line interface and the code that reads profiler output, then determine how two runs can be matched and ranked by timing differences; done means a vernier-diff command produces the illustrated ordered report.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.