Is it possible to extract only the valid data area in bcf to hdf5？
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by tracing the bcf2hdf5 conversion path and the code that reports the valid-area coordinates. Compare how masked and unmasked regions are represented in the BCF input and HDF5 output, including the all-zero invalid patterns. Done means the requested valid area can be converted without retaining the large invalid region, with the resulting HDF5 data remaining usable for EBSD maps.
Written by the indexing model from the issue text.
Description
Hi,
When I use a bruker SEM to collect EBSD data, if my actual collection area is a small area in the current display area (by mask), the area inside the mask is the valid area, and the area outside the mask is the invalid area. In fact, it will cause a lot of black invalid areas in the ipf map from ctf. At the same time, although the bcf file is very small, it will become huge after converting to hdf5, and the "pattern" of the invalid area is all 0. I would like to ask, since the bcf2hdf5 program can report the coordinates of the valid area, is it possible to convert only the valid area into hdf5 file?
Thanks!
- Dominant language
- C++
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
EchoTools/nevr-runtime#116 ·
Maintainers usually reply within 1 day
-
code-quality libc++
Difficulty 1/5 Under an hour Newbie friendliness 82/100
llvm/llvm-project#229284 ·
Maintainers usually reply within 1 day
-
test-issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
llvm/offload-test-suite#1557 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
iOS: hidden scale bar invalidates its intrinsic content size on every layout pass of MLNMapViewOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
maplibre/maplibre-native#4723 ·
Maintainers usually reply within 1 day