# ACCESS-rAM3 perturbing SSTs via OSTIA ancil

**URL:** <https://forum.access-hive.org.au/t/access-ram3-perturbing-ssts-via-ostia-ancil/6724>\
**Category:** General\
**Tags:** access-ram3\
**Created:** [28 July 2026 04:15 UTC](https://forum.access-hive.org.au/t/access-ram3-perturbing-ssts-via-ostia-ancil/6724 "2026-07-28T04:15:39Z")\
**Posts on this page:** 1\
**Showing post:** 37

<div class="post-metadata">

**Author:** ![cbengel](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@cbengel](https://forum.access-hive.org.au/u/cbengel)\
**Post date:** [13 September 2026 23:59 UTC](https://forum.access-hive.org.au/t/access-ram3-perturbing-ssts-via-ostia-ancil/6724/37 "2026-09-13T23:59:26Z")

</div>

Hi Moulik, the environment issue is solution is described here by Claire Carouge ( [ACCESS-rAM3: Files deleted with OSTIA ancillary suite - #8 by clairecarouge](https://forum.access-hive.org.au/t/access-ram3-files-deleted-with-ostia-ancillary-suite/6056/8) ).

I think given you are working with 5 dates, running the command manually is a quick work-around.

Perhaps true the PYTHONNOUSERSITE as well though and see if that solves your problem.

---

_[View the full topic](https://forum.access-hive.org.au/t/access-ram3-perturbing-ssts-via-ostia-ancil/6724)._