morgul pedestal: work on primary data, do not require VDS to merged.h5

Open
#1 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
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start at the morgul pedestal entry point and trace how it selects input data and expects merged.h5. Compare the default 4×½-module primary data with the assumed 2×1-module layout. Done means the command recognises primary data directly without requiring a VDS.

Written by the indexing model from the issue text.

Description

i.e. default is to acquire 4x½ module data sets but code still assumes 2x1 module, which we hacked by making a VDS but would be good to have morgul pedestal recognise the primary data

Dominant language
Python
Stars
0
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-morgul

All issues in DiamondLightSource/python-morgul

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.