Tree names resetted in Project HS_AG_st122_wholeCells and other Projekts #1550
Comments
|
@daniel-wer Is there any chance this could have been caused by the name tree naming schema? |
|
@tmbo This seems to be related to the backend change if I'm not mistaken? |
|
Yes it is, but it is due to the fact that we decided to drop the renaming. |
|
Will talk to Raphael Jakoby and try to find a solution |
|
Manuel Berning What I wanted to ask: Would it be easily possible to rename all trees in the DB that match the pattern "TreeXXX" to the new naming scheme (e.g. what you currently put in the filename during download)? Any caveats? This is very similar to your proposed solution #2 here: |
|
@manuel-berning no I think that is actually a quite neat solution. So the format was @manuel-berning from the top of your head, do you know if it is the complete taskId or the 6digit abbreviation? |
|
I the filename we always had the long version & I would prefer that. Patterns look right except one missing "#" before lastname in the 2nd line. 😛 (and maybe the #data should be #date). Also Daniel mentioned #user which I think is first letter of first name followed by last name. Would of course be good to keep this consistent. Mentioned in the PR by @daniel-wer Open an explorational tracing. Create a new tree and check the tree tab. The tree naming should follow the format: explorative_date_user_# Open a task. Create a new tree and check the tree tab. The tree naming should follow the format: task_taskId_user_# BTW: Would this yield unique treenames? I think that would be the most important property for me. |
|
During the update of the names in the database I would only replace „Tree“
with the naming convention. The number behind would stay the same. Hence,
it will be as unique as before ;)
Am 8. Dezember 2016 um 15:44:14, Manuel Berning ([email protected])
schrieb:
I the filename we always had the long version & I would prefer that.
Patterns look right except one missing "#" before lastname in the 2nd line.
😛 (and maybe the #data should be #date). Also Daniel mentioned #user which
I think is first letter of first name followed by last name. Would of
course be good to keep this consistent.
Mentioned in the PR by @daniel-wer <https://github.com/daniel-wer>
Open an explorational tracing. Create a new tree and check the tree tab.
The tree naming should follow the format: explorative_date_user_#
Open a task. Create a new tree and check the tree tab. The tree naming
should follow the format: task_taskId_user_#
*BTW:* Would this yield unique treenames? I think that would be the most
important property for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1550 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABDCrJEuzteoqY4jyZgq3OMIxxuajbd9ks5rGBe-gaJpZM4LG6f_>
.
|
|
@manuel-berning The frontend will NOT use the user name as you mentioned. The current implementation daniel did is Eg. it will be |
|
Ok, thanks a lot!. Sounds to me as that would solve the problem Raphael (and other members of the admin team) currently have. @heikowissler: Do you have an opinion? In general everything that is consistent is of course preferred, e.g. using a common definition of #user throughout, no matter whether back-end (generation of filenames for download I guess) or front-end (creating a new tree). Same is also true for short vs. long forms of IDs, which seem to vary throughout wK. But I guess you are aware of that yourselves. |
|
I am working on the script to change the names right now. If we wan't to change the naming convention to |
|
I'm fine with everything as long as the long ID (short should not be used anywhere) is in every tree/filename and both are unique names
…--------------------------------------------------------
Max Planck Institute for Brain Research
Department of Connectomics
Director: Moritz Helmstaedter
Max-von-Laue-Str. 4
D-60438 Frankfurt am Main
phone: +49 (69) 850033-3002
email: [email protected]
<[email protected]>
________________________________
Von: Tom Bocklisch [[email protected]]
Gesendet: Donnerstag, 8. Dezember 2016 16:38
An: scalableminds/oxalis
Cc: Heiko Wissler; Mention
Betreff: Re: [scalableminds/oxalis] Tree names resetted in Project HS_AG_st122_wholeCells and other Projekts (#1550)
I am working on the script to change the names right now.
If we wan't to change the naming convention to _tbocklisch_ for trees, we should probably do it now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1550 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABOAtaGVn8Kl_jXtG1TboOnGBohsf5jMks5rGCSQgaJpZM4LG6f_>.
|
|
@tmbo: I think making the naming should be as consistent as possible (i think so far I mostly used the tbocklisch as that is in the downloaded .nml's so I would vote for that). @daniel-wer: Could you change the pattern for newly created trees accordingly? (Basically the renaming from Tom and the pattern during creation should be the same. |
|
@heikowissler @manuel-berning so the script completed successfully and all trees have been renamed. For now with the naming scheme as it is implemented at the moment (i.e. |
|
Thanks will let Raphael Jakoby know. LG |
Good evening,
I noticed that all tree names of my project got resettet. They are now named "Tree001", "Tree002"... etc. where they used to have a unique Name identifier (including the last digets of the Task ID and a shortcut of the tracers name). With this issue it is impopssible to identify the Tasks corresponding to the traced tree in the "view all finished tasks" view.
Please rename the trees accordingly.
Thank you very much,
Raphael Jakoby
(Admin Team)
Reported by: Raphael Jakoby ([email protected]) on master
Log Time
The text was updated successfully, but these errors were encountered: