Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • est est
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • workflow
  • ewoksapps
  • estest
  • Merge requests
  • !38

Bm23 proto

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged payno requested to merge bm23_proto into master Jan 19, 2021
  • Overview 0
  • Commits 81
  • Pipelines 25
  • Changes 62

TODO

  • insure data can be read
  • add noise operation
  • add settings update from the script generated from est canvas
    • normalization range end: E_end – 100
    • Spline range end: E_end – 50
    • FT k-range end: etok(E_end-100)
    • in this can be handled by the "caller". What we need to an option to provide parameters from the command line. This can be done providing an url for now but we could also have one option per widget ? --set-xftf-params param1:value ... ?
  • reproduce data treatment
    • update larch plot made from est to fit the one from the slides. Maybe we could use Nexus attributes to define plots ?
  • add option to display flat if larch pre_edge has been call
  • add plot group in process
    • define a plot group per process
    • define silx style
    • define unit that can be used on title
    • add title to plots
    • add some 'latex attributes'
    • add unit test to insure plot, "_NexusDatasetDef" and "_NexusSpectrumDef" are correctly used
  • add possible inputs for I0, I1, I2 and mu_ref
  • update plot on est
    • add plot of noise with Y axis 'log'
  • handle HDF5 file
  • create a release version to insure we will be able to easily retrieve this version
  • enforce h5py3
  • insure qt is not requested to execute this script
  • add an energy ROI and rename current ROI "position roi"

BM23 datasets

  • "100_NO_NH3_scan_at_199 C.dat" -> silx spec file fails to read this one directly.
  • can also be accessible from Cu_CHA_68E_Proc5b.h5

display spectrum:

est xas-viewer --input-spectra 110.1/measurement/mu_trans@Cu_CHA_68E_Proc5b.h5 --input-channel 110.1/measurement/musst_eneenc@Cu_CHA_68E_Proc5b.h5 --input-energy-unit keV

image

Noise operation

image

Results are a bit different but this probably come from

Example of an output file

script_test_larch_bm23_output.h5 For now there is some attributes from "SILX_STYLE" which are not handled by the viewer as the right axis for plot.

1st generated from: script_test_larch_bm23.py image

2nd generated from test_bm23.py: output_bm23.h5

3rd generated from [test_bm23.py] : bm_test_output2.h5

final .ows file: test_bm23.ows

Edited Jan 29, 2021 by payno
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: bm23_proto