dnarayanan

error with demeshing yt in accessing deposited fields in arbitrary grids

5

### Bug report **Bug summary** When creating an arbitrary grid with demeshed yt, one cannot access the deposited gas mass from an SPH simulation. **Code for reproduction** ```python from __future__...

update gadget/gizmo front ends to only build from PartType0

2

notes in yt slack: ```YTOctree(left_edge=None, right_edge=None, n_ref=32, ptypes=None, ds=None, field_parameters=None)``` where: ``` | ptypes: list | This is the type of particles to include when building the tree. This |...

I had been thinking that we could only include the new Draine models for simulations that have a grain size distribution in them (like Smuggle; some flavors of Gizmo etc.)....

_in the pah branch:_ in__ the arepo and sph tributaries we have janky code like this: ``` reg.parameters['cell_size']=fw1.convert_to_units('cm') #so that we can have a uniform naming scheme for different front...

for active dust we have to set the size distribution by hand in parameters master. for at least arepo and I think gizmo too these aexist in the snapshot hdf5....

easy fix to implement https://github.com/dfm/python-fsps/issues/172#issuecomment-965622563

use Kubota & done as an option for AGN spectra

1

https://github.com/arnauqb/qsosed

dust masses for gizmo with OTF dust

1

right now the dust masses for gizmo/gadget datasets with on-the-fly dust won't work for `manual` mode because it will look for `PartType0`. a possible way to fix this would be:...

have code error out if metallicities exceed tabulated fsps metallcities

1

only relevant for idealized simulations, quantities (e.g.): ```disk_stars_metals = 11 # in fsps metallicity units``` or alternatively, have user put in metallicity in units of solar, and have the code...