# Making experimentation terms clearer and well-defined

**URL:** <https://forum.mergetb.net/t/making-experimentation-terms-clearer-and-well-defined/106>\
**Category:** Uncategorized\
**Created:** [July 26, 2022, 7:53pm UTC](https://forum.mergetb.net/t/making-experimentation-terms-clearer-and-well-defined/106 "2022-07-26T19:53:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![calvin](https://forum.mergetb.net/letter_avatar_proxy/v4/letter/c/f475e1/32.png) [@calvin](https://forum.mergetb.net/u/calvin)\
**Post date:** [July 26, 2022, 7:53pm UTC](https://forum.mergetb.net/t/making-experimentation-terms-clearer-and-well-defined/106/1 "2022-07-26T19:53:40Z")

</div>

I recently went through the process of setting up and provisioning 8 experiments within a short time frame, and noticed a few things about the Merge experimentation process.

Specifically, it’s not very obvious to the user as to:

1. why realization and materialization requries two separate steps
2. what realization/relinquish and materialization/dematerialization actually do and their purpose

(and why is there no parallelism between “realize” and “relinquish” like “materialize” and “dematerialize”?)

For example, a user might ask or wonder (with helpful answers from discussions with @bkocolos):

- if I dematerialize an experiment, are the expnodes imaged and saved for a quicker rematerialization like on DETERLab?

- why can’t I save a snapshot of my expnodes and restore them?

- why do I have to realize and then materalize if realizing already reserves resources on the testbed?

- why do I have to [dematerialize](https://www.mergetb.org/docs/experimentation/hello-world-gui/#dematerialize-the-experiment), and then [relinquish](https://www.mergetb.org/docs/experimentation/hello-world-gui/#relinquish-the-resources) (“derealize”) an experiment to clean it up?

Some of the concepts are buried in the documentation, and we need to push these concepts to the front and center so that users understand, at a high level, the Merge model of experimentation.

Before we do that, I also think there’s an opportunity to define and/or make the terms clearer.

For example, we could:

- alias `create` to (realize + materialize) and `destroy` to (dematerialize + relinquish)
- alternatively, instead of realize/relinquish and materialize/dematerialize, we could implement/alias `create {realization,materialization}` and `destroy {materialization,realization}`
- support custom images and snapshots
- make the “create an experiment” process as simple as possible for the user’s first project, and then introduce customization as needed

Thoughts/suggestions?
