Fit summary table.

Open
#61 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Locate the code that writes the reconstruction log and inspect how fit results are collected for each channel, timepoint, and direction. Add a final summary using the fields shown in the issue, then run the existing reconstruction or logging tests if available and verify the table appears before the completion and elapsed-time lines.

Written by the indexing model from the issue text.

Description

The more recent versions of softworx have a fit summary table at the end of the log file. This is very usful as quick glance resource to see if the fits failed catastrophically. Eg:


----------------- Reconstruction Summary -----------------
Channel 603, Timepoint 1:
Dir	Best Fit k0	Opt k0 Angle	Linespacing	Amplitude
1	0.244357	-0.697030	0.228724	0.664149
2	0.228645	-1.734281	0.228957	0.740122
3	0.086685	-2.970548	0.228820	0.764599

Channel 527, Timepoint 1:
Dir	Best Fit k0	Opt k0 Angle	Linespacing	Amplitude
1	0.078425	-0.697064	0.194127	0.761721
2	0.053312	-1.733829	0.194250	0.780785
3	0.408733	-2.941665	0.194206	0.743766

Channel 447, Timepoint 1:
Dir	Best Fit k0	Opt k0 Angle	Linespacing	Amplitude
1	0.337205	-0.708652	0.191332	0.630716
2	0.401718	-1.747677	0.191322	0.647577
3	0.137287	-2.949283	0.191064	0.550838

Channel 679, Timepoint 1:
Dir	Best Fit k0	Opt k0 Angle	Linespacing	Amplitude
1	0.140909	-0.687652	0.240964	2.063715
2	0.022379	-1.726227	0.240826	2.229488
3	0.258252	-2.971421	0.240758	2.258527


Finished SI Reconstruction: Fri Jun 14 17:35:11 2024
Elapsed Time: 0:00:37
Dominant language
Python
Stars
0
Forks
2
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/PySIMRecon

All issues in DiamondLightSource/PySIMRecon

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.