NSLS2 / NSLS2/PyXRF

DOC: Where can I find the documentation about making a .h5 file from a text file to run into PyXRF?

Open
#306 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
38
Forks
29
PR merge metrics
No merged PRs in 30d

Description

I have been looking for a long time how to correctly pass data that I have in text format to a .h5 file format. The end goal is to be able to read the .h5 file with PyXRF and get a spectrum.

Expected Behavior

When I run the next code:
xrfh5_page-0001

I get a .h5 file. When I try to read from PyXRF I would expect to see a spectrum.

Current Behavior

However, when reading the file I get a banner that says the following:
xrfmapproblem

Possible Solution

The first thing I did was read an .h5 file that does run with PyXRF. I managed to see the following:
xrfmap_page-0001

But when running the same code but with the .h5 file that I created, the following results:
NOxrfmap

I don't know what to do but I think the problem is in the way I pass the text file to .h5

Thanks!

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

Review the issue's screenshots and the documented workflow for converting text data into an .h5 file for PyXRF. Compare the created file with the working .h5 example, then clarify the required input structure and document a reproducible conversion path that PyXRF can read as a spectrum.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.