Date: Wed, 28 Sep 2011 19:07:49 -0000 (UTC)
Subject: Re: [sdss3-25mlog 274] Re: 2.5m obslog 20110927 (MJD 55832)
From: snedden@apo.nmsu.edu
Hi Russell,
The observers all know what the error message means. The issue is that we
cannot and should not touch the APOGEE data to create more space (at least
for now). That is for the APOGEE team to manage. We've been seeing the
disk-space alerts since the last APOGEE run - who is responsible for
managing APOGEE disk space? It needs to be dealt with.
Steph
> On Sep 28, 2011, at 6:08 AM, elenam@apo.nmsu.edu wrote:
>
>> We got apogee serious alert, but as we did not know
>> how to care about this, we contacted with apogee
>> team and informed them about the problem.
>> Serious apogeeql.qlDiskAlarm (Enum('Serious'), Int(853 GB))
>> Jon Holtzman confirmed that no other action is required on our
>> part at this time.
>
> This means the APOGEE QuickLook computer is running out of disk space. To
> decide if it can be ignored until morning (as opposed to having to call in
> outside help) you'd have to know the rate at which APOGEE observations
> fill up the disk. This sounds to me like an important piece of information
> to add to the observing procedures (along with the rate of filling the
> APOGEE ICC disk, since it can produce similar alarms).
>
> -- Russell
>
> _______________________________________________
> Message 274 of sdss3-25mlog - Logs of nightly APO activities.
> sdss3-25mlog@sdss3.org
> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>