Reinstate the time histogram of events

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
pandas, python
Domain
data

Research direction

Start by inspecting the current images multi and images pp commands, then search the repository history for the earlier time histogram tool. Done means reinstating a calculation that bins events by image number and produces both a PNG histogram and a CSV of bin edges and frequencies.

Written by the indexing model from the issue text.

Description

An early iteration of the Tristan tools included a time histogram tool, which disregarded the event_id information and simply binned events into time bins, equivalent to what you would get by summing the counts on each image from images multi or images pp. It is obviously a trivial calculation to bincount the image numbers, so this should be reinstated.

Output was a PNG plot of the histogram and a CSV table of bin edges and frequencies, simply created with Pandas. This seemed to provide useful functionality to I19 beamline staff and users at the time.

Dominant language
Python
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from DiamondLightSource/python-tristan

All issues in DiamondLightSource/python-tristan

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.