<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Everyone,<div class=""><br class=""></div><div class="">I’m bugging the mailing list to gather opinions from anyone interested the <a href="https://bitbucket.org/yt_analysis/yt/pull-requests/2474/wip-refactor-particle-dataset" class="">PR</a> I’m working.</div><div class=""><br class=""></div><div class="">The purpose of the <a href="https://bitbucket.org/yt_analysis/yt/pull-requests/2474/wip-refactor-particle-dataset" class="">PR</a> is to refactor the `ParticleDataset` class in yt. Currently the `ParticleDataset` is not much different from `Dataset`, but there sure are common attributes and methods specific to particle datasets that should be put in the `ParticleDataset` class. To make particle dataset better supported in yt, I plan to do the following things:</div><div class=""><br class=""></div><div class="">- Move particle specific operations from `Dataset` to `ParticleDataset`.</div><div class="">- Add some particle dataset specific properties.</div><div class="">- Gather common operations from `ParticleDataset`’s direct inheritance to `ParticleDataset` itself. Currently there are common parts in `TipsyDataset` and `GadgetDataset`’s constructor that I have figured out. There might be more.</div><div class="">- As Nathan suggested, it might be good to have an `SPHParticleDataset` for SPH codes but `ParticleDataset` for pure N-body codes.</div><div class=""><br class=""></div><div class="">If you’re interested in any of these, or have any idea to add, please feel free to leave your comments here or in the <a href="https://bitbucket.org/yt_analysis/yt/pull-requests/2474/wip-refactor-particle-dataset" class="">PR</a>.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Bili</div><div class=""><br class=""></div></body></html>