search

DCS-LCSR / SignStream3

Sign language linguistics annotation software
2 stars 0 forks source link

SS 3.4.0 - Utterances: This should not be possible #608

Open cneidle opened 1 year ago

cneidle commented 1 year ago

I don't know how this happened.

But when I reopened the file I had saved earlier, this is what I saw:

Screen Shot 2022-12-11 at 8 22 32 PM Screen Shot 2022-12-11 at 8 26 40 PM

I will email the file to you. thanks.

gregorydimitriadis commented 1 year ago

This looks like what I saw happening in https://github.com/DCS-LCSR/SignStream3/issues/562

Were the first and second utterances both named "U1" by any chance?

If not - do you recall the exact steps which led to this? (i.e. what happened in the file after it was created and before it was saved). Also any versions in use, etc.

cneidle commented 1 year ago

Hi Greg,

I did not explicitly name utterances. The numbers were automatically generated, but the name “U1” was obviously generated twice, and apparently only on the Segment tier, but not on the Temporal Partition tier, which also should not be possible.

As I said, I don’t recall what I did, and I did not notice this initially — only when RE-opening the previously saved file.

This was a file created in version 3.4.0, and then reopened using the same version.

Thanks, Carol

On Dec 13, 2022, at 11:31 AM, Greg Dimitriadis @.***> wrote:

This looks like what I saw happening in #562 https://github.com/DCS-LCSR/SignStream3/issues/562 Were the first and second utterances both named "U1" by any chance?

If not - do you recall the exact steps which led to this? (i.e. what happened in the file after it was created and before it was saved). Also any versions in use, etc.

— Reply to this email directly, view it on GitHub https://github.com/DCS-LCSR/SignStream3/issues/608#issuecomment-1349000339, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADH7NQR5RSH6I7HTEERZGPLWNCQG3ANCNFSM6AAAAAAS3K6G2A. You are receiving this because you authored the thread.

gregorydimitriadis commented 1 year ago

I'm going to test this one to see if it recurs. If so, it is definitely a severe issue that shouldn't happen.

If it is related to the other issue I linked, then that should resolve the renaming aspect of utterance name overlap, at least. But that doesn't appear to be what happened here.

cneidle commented 1 year ago

Hi Greg. There was definitely no renaming of any utterance. But it is not clear how to make this happen again... One thing that occurs to me is that I had to quit out of SignStream at some point because the main window had gotten hidden, and there was no way to show it again. It's possible that something weird happened when I quit and then chose to save just before quitting.. I would not worry about this unless it happens again... THANKS !!

cneidle commented 1 year ago

I suspect that this is related to having two utterances with the same name. How these utterances came to both be labeled U1 is a separate question... Probably related to #625. The general issue of utterance names in temporal partition and segment tier is not something I would consider to be of low severity, FWIW.