Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (775250f) to head (804d7c3).
⚠️ Report is 10 commits behind head on main.

@@            Coverage Diff            @@
##              main      #365   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          520       520           
=========================================
  Hits           520       520           

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

I reviewed the datasource in test files that ends in gr but I don't think they are suitable for the example here as we specified two spacing d and q here. Caden sent me the real example of CeO2.fq data, we have two options here: One is to add that file in the parser_data, recompress it and make a PR here; The other is to just copy the statistics for the measurement here. But I believe the real data has a very long sequence so it is safer to do it in the former way. I also ran a calculated one for CeO2in xy file format, should I also add that one into the parser-data? The data I have put here is the first three entries of the real data.

I reviewed the datasource in test files that ends in gr but I don't think they are suitable for the example here as we specified two spacing d and q here. Caden sent me the real example of CeO2.fq data, we have two options here: One is to add that file in the parser_data, recompress it and make a PR here; The other is to just copy the statistics for the measurement here. But I believe the real data has a very long sequence so it is safer to do it in the former way. I also ran a calculated one for CeO2in xy file format, should I also add that one into the parser-data? The data I have put here is the first three entries of the real data.

@cadenmyers13 for this we need diffraction datasets. Maybe not very large though if possible. so .chi or .iq or .fq

@sbillinge I sent @stevenhua0320 a .chi file and a .fq file too. I think the .chi file is what we want.

@stevenhua0320 Its been a while since I looked at this but I think the gist is to add the data to this repo so that users can grab it and run it for this example. try to fix the example and make it easy for users to run (add a link to the data or something like that).