Bug in harvest json file.
Hello Thomas,
I've noticed a bug while using indexamajig from CrystFEL v0.10.1 with --harvest-file
option - generated harvest file looks like:
{
"input": {
"highres": 6249999872.000000
},
"peaksearch": {
"method": "peakfinder8",
...,
"min_peak_over_neighbour_adu": null
},
"hitfinding": {
"min_num_peaks": 10
},
"indexing": null
"integration": null
}
so it is missing a coma after "indexing": null
and cannot be automatically decoded by json. I think this should be something relatively easy to fix?