<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yiv1115009734"><div id="yui_3_16_0_1_1456216318124_2496"><div style="color:#000;background-color:#fff;font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;" id="yui_3_16_0_1_1456216318124_2495"><div id="yiv1115009734yui_3_16_0_1_1456128170905_2081"><span>Dear Eda,</span></div><div id="yiv1115009734yui_3_16_0_1_1456128170905_2081"><span><br></span></div><div id="yiv1115009734yui_3_16_0_1_1456128170905_2081" dir="ltr"><span id="yiv1115009734yui_3_16_0_1_1456128170905_2637">I guess that the problem comes from the the ".sin" output. Unfortunately, the .sin is buggy when you are simulating a "pixelated" scanner; and regardless of phantom being imaged, the such an output provides a point-like projection image (false/wrong sinogram).<br><br>If you would still like to model a pixelated crystal, you can benefit from other output formats like ASCII or ROOT. <br><br>PS: A setDepth command (in your digitizer module) is also necessary. <br><br>Hope these help!</span></div><div></div><div id="yiv1115009734yui_3_16_0_1_1456128170905_2388"> </div><div class="yiv1115009734signature" id="yiv1115009734yui_3_16_0_1_1456128170905_2379"><div id="yiv1115009734yui_3_16_0_1_1456128170905_2387"><span style="font-size: small;" id="yiv1115009734yui_3_16_0_1_1456128170905_2386">Hojjat </span></div><div id="yiv1115009734yui_3_16_0_1_1456128170905_2651"><div id="yiv1115009734yui_3_16_0_1_1456128170905_2650"><br></div><u style="color:rgb(34, 34, 34);font-family:arial, helvetica, sans-serif;font-size:small;background-color:rgb(255, 255, 255);"></u></div></div></div></div></div></div></body></html>