# Deleting old daily 3D 0.1° data from rr6?

**URL:** <https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040>\
**Category:** Ocean\
**Tags:** data, storage\
**Created:** [16 April 2024 07:11 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040 "2024-04-16T07:11:24Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [16 April 2024 07:11 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/1 "2024-04-16T07:11:24Z")

</div>

Hi folks,

Back in 2018 I saved 26TB of 3d daily `salt`, `temp`, `u` and `v` data from `01deg_jra55v13_iaf` here  
`/g/data/rr6/cosima/access-om2-01/01deg_jra55v13_iaf`  
and it’s time to think about whether we still need it.

This was from the original 0.1° ACCESS-OM2-01 IAF run, as published in the model release paper ([Kiss et al., 2020](https://doi.org/10.5194/gmd-13-401-2020)) and is now obsolete (if you want 3d daily `salt`, `temp`, `u` and `v` you should use the newer output here instead: `/g/data/cj50/access-om2/raw-output/access-om2-01/01deg_jra55v140_iaf`).

If you have a good reason we shouldn’t delete `/g/data/rr6/cosima/access-om2-01/01deg_jra55v13_iaf`, let me know ASAP!

---

<div class="post-metadata">

**Author:** ![adele-morrison](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/adele-morrison/32/90_2.png) [@adele-morrison](https://forum.access-hive.org.au/u/adele-morrison)\
**Post date:** [16 April 2024 07:23 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/2 "2024-04-16T07:23:21Z")

</div>

Deleting sounds great! What project is rr6?

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [16 April 2024 07:30 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/3 "2024-04-16T07:30:18Z")

</div>

rr6 is a BOM project. The data was originally stored for Bluelink folks but others have also made use of it (though not recently AFAIK)

---

<div class="post-metadata">

**Author:** ![dougiesquire](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/dougiesquire/32/16_2.png) [@dougiesquire](https://forum.access-hive.org.au/u/dougiesquire)\
**Post date:** [16 April 2024 07:57 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/4 "2024-04-16T07:57:14Z")

</div>

Could it be archived to tape instead of deleted?

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [16 April 2024 22:31 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/5 "2024-04-16T22:31:46Z")

</div>

I’d only bother with that if there was a chance anyone would retrieve it again. No point if it’s a one-way trip.

---

<div class="post-metadata">

**Author:** ![adele-morrison](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/adele-morrison/32/90_2.png) [@adele-morrison](https://forum.access-hive.org.au/u/adele-morrison)\
**Post date:** [16 April 2024 23:14 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/6 "2024-04-16T23:14:26Z")

</div>

Agreed. massdata is a pain.

---

<div class="post-metadata">

**Author:** ![navidcy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/navidcy/32/101_2.png) [@navidcy](https://forum.access-hive.org.au/u/navidcy)\
**Post date:** [17 April 2024 14:22 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/7 "2024-04-17T14:22:52Z")

</div>

Did you raise it in a COSIMA meeting?

I would raise it there. Perhaps in two different meetings. I’d put an “ultimatum” e.g. something like “this data is going to be deleted on DD-MM-YYYY unless we hear someone having good reasons not to” and allow 2-3 weeks before `rm -rf ...`?

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [19 April 2024 08:40 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/8 "2024-04-19T08:40:44Z")

</div>

It looks like this rr6 data isn’t included in the main database, so it’s unlikely anyone’s using it via the cookbook.

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [9 May 2024 10:49 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/9 "2024-05-09T10:49:38Z")

</div>

3 weeks of deafening silence, so let’s delete it.

---

<div class="post-metadata">

**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\
**Post date:** [13 May 2024 02:11 UTC](https://forum.access-hive.org.au/t/deleting-old-daily-3d-0-1-data-from-rr6/2040/10 "2024-05-13T02:11:14Z")

</div>

NCI will change it to NCI-only access and then delete it after a month or so if nobody complains.
