Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

silx.io.spech5: Fixed unit cell header line interpretation #3509

Closed
wants to merge 2 commits into from

Conversation

t20100
Copy link
Member

@t20100 t20100 commented Jul 23, 2021

This PR fixes the header line that is interpreted as unit_cell, it was #G1 and is now #G2.
This looked like a bug, but if someone with good knowledge of SPECfile can check, that'd great.

Related to:

@t20100 t20100 added this to the 1.0.0 milestone Jul 23, 2021
@t20100
Copy link
Member Author

t20100 commented Jul 23, 2021

attn @newville @maurov

@t20100 t20100 marked this pull request as draft September 1, 2021 13:18
@vallsv
Copy link
Contributor

vallsv commented Sep 20, 2021

Any feed back here?

@maurov
Copy link
Contributor

maurov commented Sep 20, 2021

Hello, according to the Spec manual, #G2 is the field for the lattice constants. Personally, I would merge like this.

@t20100
Copy link
Member Author

t20100 commented Sep 20, 2021

In another documentation, the scans one, you can find:

#G1
Specifies parameters associated with the diffractometer geometry. The parameters are those from the U[] array, which include lattice constants and orientation reflections.

We've checked what the macro does, and it saves the U[] array as #G1 and there is no #G2.

BTW, support of unit_cell as #G1 was introduced in #722 and it is like that since 4 and a half years.

@maurov
Copy link
Contributor

maurov commented Sep 20, 2021

@t20100 I have no strong opinion on this, as I have never used #G* parameters myself. Maybe @vasole knows some beamlines using them.

@t20100
Copy link
Member Author

t20100 commented Sep 20, 2021

I have no strong opinion on this,
@maurov me neither!

Documentation is inconsistent, but the code of the SPEC macro that BCU just checked is clear: it is using #G1, so I'm closing this.

@t20100 t20100 closed this Sep 20, 2021
@newville
Copy link

@t20100 @maurov Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants