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

Requirement: Fix byte order of binary portions of header; define byte order of payload via encoding values #19

Open
krischer opened this issue Jan 3, 2018 · 12 comments

Comments

@krischer
Copy link
Contributor

krischer commented Jan 3, 2018

Simplification of MiniSEED2: Fix byte order (e.g. little endian) of binary portions of header; define byte order of payload via encoding values.

@chad-earthscope
Copy link
Member

chad-earthscope commented Jan 9, 2018

In the July 2017 discussion on this topic support for a fixed by order was unanimous among those involved. It was not decided which byte order should be chosen.

I have a slight preference for little-endian as that is the native order for most of the hardware that will be reading this data for the foreseeable future. One wrinkle is that the Steim encodings are only allowed to be big-endian.

@krischer
Copy link
Contributor Author

krischer commented Jan 9, 2018

👍 for little endian.

@krischer
Copy link
Contributor Author

Summary

(Please let me know if I missed a point or misunderstood something)

Please vote on:

  1. Should the byte-order of the header be fixed? (Yes/No)
  2. Assuming yes on (1): What should it be? (Little endian / Big endian)
  3. Should the byte order of the data be defined by the encoding? Already implicit for some in miniSEED 2.x; others require some additional specification. (Yes/No)

@crotwell
Copy link

1 yes
2 little
3 yes - by this you mean the 2 might be "big endian 32 bit ints" and 47 might be "little endian 32 bit ints" (I am making up numbers of course) and there would be no number for "little endian steim1" as that doesn't exist.

@ketchum-usgs
Copy link

  1. Yes
  2. No strong opinion - network byte ordering (big endian) is always nice.
  3. yes

@chad-earthscope
Copy link
Member

  1. Yes
  2. Little
  3. Yes.

@kaestli
Copy link

kaestli commented Jan 30, 2018

1 yes
2 little
3 yes

@ozym
Copy link

ozym commented Jan 30, 2018

  1. Yes
  2. Little
  3. Yes

@claudiodsf
Copy link

  1. Should the byte-order of the header be fixed? (Yes/No)

Yes

  1. Assuming yes on (1): What should it be? (Little endian / Big endian)

No strong opinion

  1. Should the byte order of the data be defined by the encoding? Already implicit for some in miniSEED 2.x; others require some additional specification. (Yes/No)

Yes

@ihenson-bsl
Copy link

  1. Yes
  2. Little endian
  3. Yes

@ValleeMartin
Copy link

  1. Yes
  2. No opinion
  3. Yes

@JoseAntonioJara
Copy link

  1. Yes
  2. No strong opinion
  3. Yes

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

No branches or pull requests

10 participants