Skip to content

Clarify status of Kim Lab Developmental CCF v001 atlas - #529

Open
PolarBean wants to merge 1 commit into
mainfrom
kim-atlas-fix
Open

Clarify status of Kim Lab Developmental CCF v001 atlas#529
PolarBean wants to merge 1 commit into
mainfrom
kim-atlas-fix

Conversation

@PolarBean

Copy link
Copy Markdown
Member

I don't believe this atlas was superseded by a different one. They're just different. This one is available in 10 microns in Allen space. The other atlas is a different modality and lower resolution.

@adamltyson

Copy link
Copy Markdown
Member

I think this is a semantic point, but pretty sure the "new" version is an update to the older version:

  • It was built by the same people
  • The name is the same
  • The version is bumped (sort of)
  • It came out later
  • The modalities are mostly the same
  • It has the same developmental timepoint plus six more

As far as I know, v001 was an early version they released on the way to building (and publishing) v1.0

There is also the "epDevAtlas", but I think that one is different, and not in BrainGlobe.

@adamltyson

Copy link
Copy Markdown
Member

Although digging a bit more, the epDevAtlas may effectively be the next version of this atlas.

@PolarBean

Copy link
Copy Markdown
Member Author

Yes you're right epdev is the newer version of this. Ill update the blog to reflect this. nice catch.

@PolarBean

Copy link
Copy Markdown
Member Author

ah it seems we dont yet have epdev

@adamltyson

Copy link
Copy Markdown
Member

I think it may be more for the data API (although I haven't looked into it). not sure how much the underlying template and annotations have changed.

@adamltyson

Copy link
Copy Markdown
Member

Also which blog?

@PolarBean

Copy link
Copy Markdown
Member Author

epdev has many templates for different ages that we dont have so its definitely needed for the atlas api. Maybe this should stay though if its identical the epdev p56. By blog I meant atlas description soz.

Maybe we should merge this as is? would you like a sentence about the epdev even though its not yet integrated?

@adamltyson

Copy link
Copy Markdown
Member

epdev has many templates for different ages that we dont have so its definitely needed for the atlas api.

Oh yeah, I saw it has the same number of ages, but didn't realise they were different ones. There is also DevATLAS which seems to be distinct too.

Maybe we should merge this as is?

See my comment above, I think (although very happy to be proved wrong) that the statement you're deleting is valid.

@PolarBean

Copy link
Copy Markdown
Member Author

When reading "This atlas is now superseded by its 1.0.0 version but continues to be available for reproducibility and archive reasons."

since we have Kim Lab Developmental CCF v001 (P56) in the API I think theres room for confusion.

Also if the P56 epdev atlas is literally just this atlas then it hasnt been superseded? This atlas is still relevant and is not only in the API for reproducibility and archive reasons

@PolarBean

Copy link
Copy Markdown
Member Author

For this atlas to be superseded we would need to package the epdev atlas p56 (which may be identical) and have a "epdev_mouse_p56" entry in the API

@adamltyson

Copy link
Copy Markdown
Member

When reading "This atlas is now superseded by its 1.0.0 version but continues to be available for reproducibility and archive reasons."

since we have Kim Lab Developmental CCF v001 (P56) in the API I think theres room for confusion.

I don't understand. As far as I know, v001 is superseded by v1.0.0, so this is all correct and as it should be.

@PolarBean

Copy link
Copy Markdown
Member Author

V1.0.0 is not the same as epdev atlas. V1.0.0 is the DevCCF https://doi.org/10.1038/s41467-024-53254-w which is distinct from epdev atlas https://doi.org/10.1101/2023.11.24.568585

epdev supersedes V001 but epdev is not yet in the BrainGlobe atlas API. It is very confusing as these two atlases came out of the same group at similar times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants