Hi Britton and yt-users,

Thank you for your advice. I tried including find_outputs=True again, no difference. I tried creating redshift dump directories and copying the dataset parameter files there (FYI that gives the error: P005 yt : [ERROR    ] 2019-05-24 10:21:08,895 Couldn't figure out output type for RD0017/RedshiftOutput0017).  I tried putting the location of the dataset parameter files in storage, that led to the same result as not having the files mentioned at all.

Since then I have given up on making this work and have copied the files back from storage and tried running from the beginning. That results in this error being produced. Has anyone come across this error and knows what causes it? I had previously run rockstar successfully on this dataset before moving the files. Any suggestions would be appreciated.

Kind regards,
Carla

Am Di., 21. Mai 2019 um 13:18 Uhr schrieb Britton Smith <brittonsmith@gmail.com>:
Hi Carla,

It looks like the time-series object is failing to find any valid datasets. You can test this by removing the call to the RockstarHaloFinder and doing this after es.get_time_series:
for ds in es:
    print (ds)

I'm guessing that will not print anything. I imagine you'll just need to put the find_outputs=True back, but if that's not the case, then something has changed about the way the datasets are being named such that the EnzoSimulation can't find anything of the names it expects.

Once you get that fixed, I think the other issue you'll encounter is that Rockstar will be confused about which dataset on which to resume. You'll need to make sure that the datasets.txt file has all the previous datasets in it. I think the only way to accomplish this is to replace the original dataset directories and just put the dataset parameter files inside them.

Britton

On Mon, May 20, 2019 at 3:30 PM C Bernhardt <bernhardt.phd@gmail.com> wrote:
Dear yt-users,

I am using this script to run Rockstar and it has worked great for me for years. Here is the situation now: I ran rockstar a few weeks ago and since then have several additional enzo data dump outputs I would like to add to my merger trees (done with consistent-trees). To meet data quota requirements, I needed to move several of my outputs to storage (already got the rockstar outputs on these), which I believe is causing my rockstar restart to fail (see error here). 

In the script mentioned above, I tried removing find_outputs=True on line 51 and adding the keyword initial_redshift=11.749 to get_time_series() on line 59. I keep getting the same error. I have also updated datasets.txt as well as rockstar.cfg and restart.cfg to the desired RESTART_SNAP and NUM_SNAPS.

What am I missing? Is there a way to run a restart on Rockstar with some of the previous files (already processed by rockstar) missing? Thanks in advance.

Kind regards,
--
Carla Bernhardt
PhD Student
Universität Heidelberg
ZAH Institut für Theoretische Astrophysik
_______________________________________________
yt-users mailing list -- yt-users@python.org
To unsubscribe send an email to yt-users-leave@python.org
_______________________________________________
yt-users mailing list -- yt-users@python.org
To unsubscribe send an email to yt-users-leave@python.org


--
Carla Bernhardt
PhD Student
Universität Heidelberg
ZAH Institut für Theoretische Astrophysik