Charu Jain

I have nine years of experience. My first six years were in software engineering, where I worked on front-end web development and deployment activities. After that, I completed my master's for two and a half years and specialized in machine learning. One and a half years of my master's program involved working on a project related to medical images, which included DICOM files and the creation of tools for image segmentation. After that, I worked with back-end technologies, where I worked on point cloud image processing.

Well, I have built an app for a web application that allows editing 3D segmentations using 3D Slicer software. 3D Slicer has an API that I used to build web components which could access the machine learning algorithm and predict the segmentation on the web app. We were also able to edit using the APIs, applying web components that could edit the images on the screen. I was able to do this using the 3D Slicer API.

In what ways would ES6 and ReactJS aid me in building web apps? Well, ReactJS will provide web components which would help me in building the web application. ES6 provides a standardized way of doing the same. So using the web components provided by ReactJS, I will be able to provide interactivity with the application.

Cornerstone.js is a JavaScript library that helps interact with medical images. It facilitates working with medical images, and it helps in visualizing 3D images in different directions and formats. A framework like Cornerstone.js, in combination with React.js, can be used for loading DICOM files or NIFTY files and visualizing them in 3D space, including XYZ directions, the XY plane, the YZ plane, the ZY plane, or as a 3D rendering format.

The project structure. Well, the project structure that I use is that I keep the constant variables in a separate file. And I organize my project in such a way that it is that the components are reusable and they are upgradable. And all the components are also unit tested as well as system tested end to end so as to build a scalable platform for a front-end application.

Can you provide an example of a complex front-end feature you developed in a technology stack that you used? Well, this was a long time back when I was working in web application development for a banking application. We were able to build a login feature with normal web components for login and transition between two different applications, where you could roll down and dynamically load more content on the screen.

Consider the below Python function that loads DICOM image and visualizes 3D segmentation using what potential issues can you spot and how can you suggest to improve? So it is able to read the file and return the pixel array. Well, there should be a check whether the data which is loaded is present or not. So there needs to be an exception which needs to be added. So that there is a fallback in case the file is not present. There needs to be an exception rule in load image while it's loading the file. That's all.

Review the following charges against a student that uses consumption as a premedical measure and whether you might be wrong with it. Load image should be present before enabling the element Thank you for watching!

In the current project at Vihant where I was working, we had to alter the image displayed in 2D to 3D, and it also had to highlight the 3D points on the screen where a foreign object was present. Working with 3D data using a new library was a difficult task, so the existing 2D image loading had to be changed to 3D image loading, as well as rendering that on a 3D view box, which was a challenging situation.

What are the strategies you have employed to ensure a small functional GPU-dependent browser? Well, GPU-dependent browser application, I have used for 3D rendering of images or 3D reconstructed images that I was working with. So, we used libraries that also provided functions for working on the GPU. So, the idea was that if a GPU is available, then it works on the GPU; else, there is a fallback to the CPU in case GPU capability is not present. To ensure the smooth functioning of the GPU-dependent browser application, we had to make it independent of the hardware being used. So, the idea was that we were using open-source libraries so that they are not dependent on vendor-specific hardware configurations. So, we were using open-source libraries for GPU-based applications.