[atlas] Fwd: Re: Measurements delete and ping issue

I did not copy the list on this message and then realised that it is a
generic answer that deserves to be seen and archived here.

Daniel


-------- Forwarded Message --------

Subject: Re: [atlas] Measurements delete and ping issue
To: Andrea Consadori <andrea.consadori at hotmail.it>
References: <DUB126-W888F5B62064D1CE913A99DE0000 at phx.gbl>
From: Daniel Karrenberg <daniel.karrenberg at ripe.net>
Message-ID: <565C9760.2050704 at ripe.net>
Date: Mon, 30 Nov 2015 19:37:20 +0100


On 30.11.15 15:42 , Andrea Consadori wrote:
> 
> 
> Hi all,
> i just start using proble atlas and i found is not possible to delete
> Stopped measurements from web, it's normal?
> i try to search on old mailing list messages and seems to be and old
> issue but i still cannot delete stopped masurements
> (for example ids: 3050379
> <https://atlas.ripe.net/measurements/3050379/>, 3034900
> <https://atlas.ripe.net/measurements/3034900/>)
> ...

Andrea,

An important idea behind RIPE Atlas is that all results are re-useable.

Therefore we store the results of *all* measurements as long as we
possibly can because those results can be useful for other researchers
even if they did not run the measurements themselves.

Each result says something about the packet flow in the Internet at the
particular time it was obtained. There is no way we can foresee how
these results can help to answer interesting research questions and help
us to understand the Internet packet layer better than we do now.

For a recent example of this, please see
https://labs.ripe.net/Members/becha/ripe-atlas-tools-hackathon-results
"ASN Tryst".

Therefore we do not provide the functionality of deleting measurements.
The only way we foresee that results can be deleted is if we run out of
storage space.

Of course that one has to be careful to select the measurements one
wants to re-use according to the question one wants to answer. Your
measurement shows this very well. I do not recommend using your results
unless the question is about reachability with RTTs under 6ms.

I hope this answers your question

Daniel
(co-inventor of RIPE Atlas)