Project: Automated Artifact Detection and Annotation in LibreHealth Radiology

Projects Radiology
, , ,
23

Hi @sunbiz as the bower registery is dead i updated the dependencies using their github urls with the same versions as earlier and opened an MR.

1 Like
24

@TejasSA88 Think of the tooling that would make it easy for people to test what you’re working on, and this would be like, for example, a good Docker where people can just see what your updates are. I think that makes it easy to assess and give you feedback.

1 Like
25

Sure @judywawira i will be doing that one

26

Hi @Rohan.isaac27 @sunbiz, if you both are free this weekend i would like to schedule a call so that i can discuss the weekly goals and also the structure of the program also to clarify some doubts.

@sunbiz I have opened an MR regarding the Bower registery offline issue Iam not sure if i followed the correct process of opening an MR so please correct me if iam wrong.

MR URL: Updates bower.json dependencies to use direct GitHub URLs to fix the broken central Bower registry during Docker builds. (!79) · Merge requests · LibreHealth / LibreHealth Radiology / lh-radiology · GitLab

28

Hi Everyone below are the things which i have done so far.

  • The OHIF Viewer was using the Bower package registry as it was deprecated it broke the container builds. So I manually updated the bower.json dependencies to pull directly from GitHub URLs. The MR for this issue got merged.
  • The OHIF Viewer was not able to load the DICOM data as it was pulling the frozen image from the gitlab registery.
  • I have reported the frozen image issue to @r0bby. In the meantime, to keep my development completely running, I am running the backend databases via Docker and spinning up the Meteor frontend locally. Everything is connecting perfectly and I am fully unblocked to write code
29

Hi @sunbiz @Rohan.isaac27 for the coding period I have planned to do a few things mentioned below for the starting of my coding period. Before the coding period starts I will be testing and looking into the codebase as to develop the following features and the FastAPI server later I need to draft an architecture and make sure that none of the data pipelines collide.

  • WEEK 1: I will create a JavaScript object which will hook into the OHIF and Meteor architecture. I plan to add a new Find Similar Artifacts tool in the toolbarsection.js It will integrate with the existing doctors workspace. planned to implement a capture phase event listener on the new button.
  • WEEK 2: I planned to use the already existing RectangleRoi tool in Cornerstone.js to extract the start, end of the region in the x and y axis. I will be implementing a UI error handler to prevent empty payloads. I will also be implementing an environment fallback pattern so the frontend can run in production without any changes.

As we come to the Dataset I will be using some external ones for the testing purposes. Also for the selection of the ROI I have planned to use the existing RectangleRoi tool what are your views on it.

Tell me if there are any updates in the plan that you suggest so that I can make changes before the coding period begins. I will be posting the full planning and the new data pipeline architecture in a couple of days.