[Mesa-users] writing pulse data with empty profile_columns.list?

[Josiah Schwab]

Hi Joel,

I have a general I/O inquiry: it seems that when I provide an empty
> profile_columns.list, no profilexxx.data files will be written even
> with write_profiles_flag set to true (I couldn't find documentation
> about this).


Yes, I think that's true.  And that behavior makes sense to me; no columns,
no file.  Would you want a file with just the header and no columns in your
use case?

However, the format of pulsation data (e.g. FGONG or GYRE)
> do not depend on profile_columns.list, but will also not be written out
> when profile_columns.list is empty. I can't find a way to change this
> behaviour in an inlist, so right now I think I will directly call
> export_pulse_data in extras_finish_step (in run_star_extras.f). Before
> I actually commit to that, does anyone have suggestions for a better
> way of doing this?
>

Looking at the code in star/private/profile.f90, we're bailing out right
away if there are zero profile columns and so never making it to the part
where we write the pulsation data.  So I don't think there's any way to fix
that in an inlist.

Your work-around seems good to me.  But I'll check to see if we can easily
rearrange the code to allow your use case in a future release.

Josiah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20200130/5fc808d3/attachment.htm>