ytdata IOHandlers: data_file index ranges?

[chrishavlin]

In working on #4595 and #4565, I found that the _read_particle_coords and _read_particle_fields implementations don't generally use the data_file.start and data_file.end indices when looping over chunks. For IOHandlerYTDataContainerHDF5, this seemed like a clear bug, so #4595 only fixes it for that handler.

Looking through the other handlers -- it looks to me like the IOHandlerYTSpatialPlotHDF5 (link to code) implementations of _read_particle_coords and _read_particle_fields should be updated to use the start and end index ranges as well. Anyone have thoughts on that?

I think the other classes should be OK since they don't over-ride the particle reader functions.

[chrishavlin]

Pinging a few folks who might have insight here: @brittonsmith @matthewturk

[brittonsmith]

This is most likely an oversight from when file chunking was implemented. If it's not using start and end, this probably needs to be fixed.

[chrishavlin]

OK, I'll get in a similar fix to use the index ranges then. Thanks!

[brittonsmith]

Thanks for taking care that!