# POP implementation in ACCESS-ESM3: inline vs separate executable

**URL:** <https://forum.access-hive.org.au/t/pop-implementation-in-access-esm3-inline-vs-separate-executable/1807>\
**Category:** CABLE\
**Tags:** notes, cable4-planning\
**Created:** [12 February 2024 22:55 UTC](https://forum.access-hive.org.au/t/pop-implementation-in-access-esm3-inline-vs-separate-executable/1807 "2024-02-12T22:55:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![clairecarouge](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/clairecarouge/32/380_2.png) [@clairecarouge](https://forum.access-hive.org.au/u/clairecarouge)\
**Post date:** [12 February 2024 22:56 UTC](https://forum.access-hive.org.au/t/pop-implementation-in-access-esm3-inline-vs-separate-executable/1807/2 "2024-02-12T22:56:53Z")

</div>

@inh599 @MartinDix @Jhan In the post above I tried to summarise our meeting about POP inline or 2 executables. I’ve made a post a wiki, don’t hesitate to edit if I missed something or mischaracterized anything.

---

_[View the full topic](https://forum.access-hive.org.au/t/pop-implementation-in-access-esm3-inline-vs-separate-executable/1807)._