ring artifact on ge lightspeed 16 slices ct scanner
December 04, 2023 11:30
Hello, just to comment about a GE lightspeed 16 slices tomograph that has an artifact problem in the image. I already ran the test in das tools and it sends me an error with a das converter card 9. I change card 9 and the artifact continues but now it shows me I change card 23 to card 23 and the artifact continues but now card 87 shows me wrong I change card 87 and the artifact continues and now card 5 shows me I change the card and the artifact continues, in total I have already changed 8 cards and I continue As if it were a chain reaction, the fact is that I only got a bad card when I ran the test. Does anyone know if there is something like that or have they already gone through this?
re: ring artifact on ge lightspeed 16 slices ct scanner
December 11, 2023 10:47
I'm not sure what type artifact you have. It could be calibrated in during fast cals. Dose it happen at all kvp's? You can restore a cal file from prior to the problem and run only das gain cals before scanning. This would have been caused by an intermittent bad board. If it's rings you need to do two scans to see the individual detector rows. Axial/1.0 sec/kvp and ma of problem/16 rows/16 i/.625mm one set of 16 images and the same at 1.25mm. this will cover the whole das. The inside 16 A and B rows are .625mm. The outside 8, 4 A rows and 4 B rows are 1.25mm. Use scan analysis under diagnostics to view these scans. Choose the scan and witch set you want to view, plot MSD, convoluted data correction. View each row 8A through 8B individually looking for a spike that would be your ring. this row should correspond to the image number that you saw the ring in. Place your pointer on the spike and get the "das" channel number(not detector channel) for the row you are viewing. Go to das architecture and put in the row and channel to determine the board with the issue.
HIGH QUALITY fully tested & refurbished systems to manufacturer specifications like new. Installation & service support worldwide. Parts & tubes in stock with warranty. Sales@Elsmed.com
Miguel Chavira
ring artifact on ge lightspeed 16 slices ct scanner
December 04, 2023 11:30
Hello, just to comment about a GE lightspeed 16 slices tomograph that has an artifact problem in the image. I already ran the test in das tools and it sends me an error with a das converter card 9. I change card 9 and the artifact continues but now it shows me I change card 23 to card 23 and the artifact continues but now card 87 shows me wrong I change card 87 and the artifact continues and now card 5 shows me I change the card and the artifact continues, in total I have already changed 8 cards and I continue As if it were a chain reaction, the fact is that I only got a bad card when I ran the test. Does anyone know if there is something like that or have they already gone through this?
thank you
Miguel Chavira
to rate and post a comment
Claude Coelo
re: ring artifact on ge lightspeed 16 slices ct scanner
December 06, 2023 10:51
Hello
What is the model of DAS ?
MDAS or GDAS?
to rate and post a comment
ALLEN GODFREY
re: ring artifact on ge lightspeed 16 slices ct scanner
December 11, 2023 10:47
I'm not sure what type artifact you have. It could be calibrated in during fast cals. Dose it happen at all kvp's? You can restore a cal file from prior to the problem and run only das gain cals before scanning. This would have been caused by an intermittent bad board. If it's rings you need to do two scans to see the individual detector rows. Axial/1.0 sec/kvp and ma of problem/16 rows/16 i/.625mm one set of 16 images and the same at 1.25mm. this will cover the whole das. The inside 16 A and B rows are .625mm. The outside 8, 4 A rows and 4 B rows are 1.25mm. Use scan analysis under diagnostics to view these scans. Choose the scan and witch set you want to view, plot MSD, convoluted data correction. View each row 8A through 8B individually looking for a spike that would be your ring. this row should correspond to the image number that you saw the ring in. Place your pointer on the spike and get the "das" channel number(not detector channel) for the row you are viewing. Go to das architecture and put in the row and channel to determine the board with the issue.
to rate and post a comment