So, is it tracing or tracking? Or both?

[sbarber2]

Hey folks, is it just me, or does it make you crazy that we're using the words tracing and tracking more or less interchangeably and inconsistently in the webapp (and maybe throughout the Plant Tracer project as a whole)?

I remember Eric saying that the original name for the project was going to be Plant Tracker but the name of the project/app was changed to Plant Tracer for (IIRC) reasons of potential trademark confusion/infringement. That "tracking" was the nomenclature used in the academic community but tracing is what we were using primarily to avoid the trademark issue.

So, I don't have a dog in that race, but I do like as a matter of software engineering and consistent user communication that we should pick a term and stick with it. Especially since we haven't written docs yet and are just about to!!

For example, currently on the analyze page, there's a frequently seen text message that says

"Movie #XX is traced! Check for errors and retrace as necessary."

But the way to 'trace' a movie is to press the 'track movie' button.

Arrgh.

So, discuss. Let's pick a term and stick with it?

Questions for all:

Is there a difference in this application domain between tracking and tracing? If so, what is it?

If not, which term shall we use within the webapp and associated documents?

Thanks for your consideration.

[sbarber2]

BTW I know that within the dev group we have discussed this before but I also know we have never resolved it. No shade especially to Simson for the current implementations. Just one of those things.

[simsong]

I think that the traces are what’s left when you draw the tracks.

…

On Sat, Sep 7, 2024 at 4:20 AM Steve Barber ***@***.***> wrote: BTW I know that within the dev group we have discussed this before but I also know we have never resolved it. No shade especially to Simson for the current implementations. Just one of those things. — Reply to this email directly, view it on GitHub <#516 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMFHLG7JE6EI34T2OQJCSDZVLORPAVCNFSM6AAAAABNZ6APYOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJXGY2TQNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[JoAnnJuzefyk]

That leads us back into circle.
But maybe logically tracking leads to a trace.
Plant Tracer or Plant Tracker? Not that the name would change.
How about referring to the act of following the apex as tracking, hence 'track movie' button. While referring to results as a trace. Then the other direction - "Movie #XX is traced! Check for errors and retrace as necessary" should be ...retrack as necessary.
The meaning of the different terms could be stated in the intro/goal section.
I hope that helps.

[ericdbrenner]

I think you all raise good points.
I did a quick search of the web and it seems that "plant tracker" has become a term commonly used to describe methods that are used to identify, name and keep track of plants (species usu.). But we have been using the term "tracer" for quite some time and so perhaps we stick with this. So where it says "track" as a button it would be more consistent to stake trace. The problem though becomes when we consider the operation esseintally does both. We trace the movement of the plant, but we also track how it has move, similar to a hunter tracking a bunny rabbit. Tracing simply follows the path. Tracking determines where it has been. Here's an idea, perhaps we have the button say, "trace and track"? Thoughts?

[sbarber2]

Lovely. So just to be sure I understand: That message becomes not: "Movie #XX is traced! Check for errors and retrace as necessary" but rather: "Movie #XX has finished tracking! Check for errors and re-track as necessary" as *trace* is no longer a verb in our working project vocabulary. That is, a movie may have-a trace, but only after it has been tracked, and it may never *be traced* as that has no meaning. Yes?

…

-Steve

On Sat, Sep 7, 2024 at 9:38 AM JoAnn Juzefyk ***@***.***> wrote: That leads us back into circle. But maybe logically tracking leads to a trace. Plant Tracer or Plant Tracker? Not that the name would change. How about referring to the act of following the apex as tracking, hence 'track movie' button. While referring to results as a trace. Then the other direction - "Movie #XX is traced! Check for errors and retrace as necessary" should be ...retrack as necessary. The meaning of the different terms could be stated in the intro/goal section. I hope that helps. — Reply to this email directly, view it on GitHub <#516 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFQOB6RYAQLYDQVGPIFI53ZVL6TZAVCNFSM6AAAAABNZ6APYOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJXG4YTENA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[simsong]

Yes. You re-track to create a new trace. ? On Sat, Sep 7, 2024 at 8:57 AM Steve Barber ***@***.***> wrote:

…

Lovely. So just to be sure I understand: That message becomes not: "Movie #XX is traced! Check for errors and retrace as necessary" but rather: "Movie #XX has finished tracking! Check for errors and re-track as necessary" as *trace* is no longer a verb in our working project vocabulary. That is, a movie may have-a trace, but only after it has been tracked, and it may never *be traced* as that has no meaning. Yes? -Steve On Sat, Sep 7, 2024 at 9:38 AM JoAnn Juzefyk ***@***.***> wrote: > That leads us back into circle. > But maybe logically tracking leads to a trace. > Plant Tracer or Plant Tracker? Not that the name would change. > How about referring to the act of following the apex as tracking, hence > 'track movie' button. While referring to results as a trace. Then the other > direction - "Movie #XX is traced! Check for errors and retrace as > necessary" should be ...retrack as necessary. > The meaning of the different terms could be stated in the intro/goal > section. > I hope that helps. > > — > Reply to this email directly, view it on GitHub > < #516 (reply in thread)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAFQOB6RYAQLYDQVGPIFI53ZVL6TZAVCNFSM6AAAAABNZ6APYOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJXG4YTENA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#516 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMFHLAR7KD2FNEUJI62VQLZVMO4JAVCNFSM6AAAAABNZ6APYOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJXG43TSNY> . You are receiving this because you commented.Message ID: ***@***.***>

[simsong]

Let’s go with a “trace” button.

…

On Sep 19, 2024, at 2:51 PM, ericdbrenner ***@***.***> wrote: I think you all raise good points. I did a quick search of the web and it seems that "plant tracker" has become a term commonly used to describe methods that are used to identify, name and keep track of plants (species usu.). But we have been using the term "tracer" for quite some time and so perhaps we stick with this. So where it says "track" as a button it would be more consistent to stake trace. The problem though becomes when we consider the operation esseintally does both. We trace the movement of the plant, but we also track how it has move, similar to a hunter tracking a bunny rabbit. Tracing simply follows the path. Tracking determines where it has been. Here's an idea, perhaps we have the button say, "trace and track"? Thoughts? — Reply to this email directly, view it on GitHub <#516 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMFHLDZHYG5EWOK2EINPQLZXMML3AVCNFSM6AAAAABNZ6APYOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRZGY4TINA>. You are receiving this because you commented.