You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered that the default settings for ezpadova are set to:
TP-AGB -- Not resolve thermal pulses (n_inTPC = 0)
M-star Circumstellar Dust -- 60% Silicate + 40% AlOx as in Groenewegen+06 (dust_sourceM = dpmod60alox40)
C-star Circumstellar Dust -- 85% AMC + 15% SiC as in Groenewegen+06 (dust_sourceM = AMCSIC15)
The circumstellar dust only affects the photometry that we ignore, so OK to ignore these for our purposes.
The form's current (v3.0) default parameters are n_inTPC=10 and no circumstellar dust for either M or C-stars. I suggest we adopt these new default choices. Please note that by resolving the TPs, a large number of additional points/samples during the AGB phase, increasing the total samples (and grid size) by ~50%.
Here are a CMD and HR diagram showing the difference between resolution of 0 (big points) and 10 (small points):
@marthaboyer: do you have an opinion on the TP resolution?
Once decided, I will edit the relevant files and submit a PR.
The text was updated successfully, but these errors were encountered:
Is there a way to expose these parameters to the BEAST such that if a user wanted more sampling on the TP-AGB and/or circumstellar dust they could indicate this?
Once the AGB atmospheres are in, it makes sense to increase the resolution. And at that point, we probably should set the defaults to some kind of dust, though I'd vote for one of the options from Nanni et al. Or if we leave the default to no dust, then I agree with Karl that we need to expose those parameters.
I discovered that the default settings for ezpadova are set to:
The circumstellar dust only affects the photometry that we ignore, so OK to ignore these for our purposes.
The form's current (v3.0) default parameters are n_inTPC=10 and no circumstellar dust for either M or C-stars. I suggest we adopt these new default choices. Please note that by resolving the TPs, a large number of additional points/samples during the AGB phase, increasing the total samples (and grid size) by ~50%.
Here are a CMD and HR diagram showing the difference between resolution of 0 (big points) and 10 (small points):


@marthaboyer: do you have an opinion on the TP resolution?
Once decided, I will edit the relevant files and submit a PR.
The text was updated successfully, but these errors were encountered: