-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: feat 194 class based color settings - bulk annotations #213
base: master
Are you sure you want to change the base?
Conversation
Visit the preview URL for this PR (updated for commit 559ebce): https://idc-external-006--idc-slim-preview-kk0jkjse.web.app (expires Fri, 02 Aug 2024 13:27:32 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 88aacecd98ba54d2f9c8d201a9444e43d1ad8307 |
4a1ce3a
to
a3a3f07
Compare
@fedorov can you give me an example of a server url you're trying to use? |
|
You have to add a /dicomWeb at the end (if you haven't) When you do that we're getting a 401 error, probably because this dataset requires google authentication but the config file the environment is using does not ask you to login with google. We're seeing how to change this right now... I'll let you know. |
Yes, you also should add the prefix. The full url is this: |
@pedrokohler whats the state on this one? |
7778418
to
2937dde
Compare
1594960
to
493d19c
Compare
@igoroctaviano as mentioned in slack I was not able to use the "live" channel id... however we can still try some other custom name. I had used idc-slim-preview for the channel id and it seems to generate a fixed URL, even though it has random bunch of characters at the end, I think it does not change. At least it hasn't with my tests. We can give it a try and add the URL to the GCP permissions so we can try to authenticate. |
Sounds good, please address the tests so we can merge. |
493d19c
to
66c758d
Compare
66c758d
to
170dca8
Compare
@fedorov this can now be tested with the dataset you required. Please do and let us know if we can merge. |
Per discussion in slack, it appears that currently this feature supports coloring of the annotation groups that come from bulk annotation modality (ANN). It should be able to handle annotations that come from SR, and allow per type/category coloring. This is a representative sample that can be used to drive the development: https://idc-external-006--idc-slim-preview-kk0jkjse.web.app/studies/2.25.155017484756498730492136597238994838876/series/1.3.6.1.4.1.5962.99.1.3434988325.342625608.1687062201125.4.0. |
Per discussion in slack, I suggest we do the following. Let's shelve this current PR for now, and start a new PR that adds these features for SR annotations, into a dedicated new section, reusing as much from the current PR as makes sense. At a later time, when there is a need, we can come back to the ANN PR, and either add its features into a new section, or merge with the SR annotations section. As @pedrokohler said, it's a good compromise... it won't make us waste what we have and we can make progress without much difficulty. |
Adding the ability to edit annotation groups colors based on their categories and types. Solves #194.
Screenshare.-.2024-06-10.12_43_53.PM.mp4