# Support for .AIM/.isq files generated on Scanco microCT

**URL:** <https://discourse.slicer.org/t/support-for-aim-isq-files-generated-on-scanco-microct/6261>\
**Category:** Development\
**Created:** [March 24, 2019, 2:23pm UTC](https://discourse.slicer.org/t/support-for-aim-isq-files-generated-on-scanco-microct/6261 "2019-03-24T14:23:24Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 17, 2019, 4:18am UTC](https://discourse.slicer.org/t/support-for-aim-isq-files-generated-on-scanco-microct/6261/26 "2019-05-17T04:18:28Z")

</div>

> [@muratmaga](#):
>
> Slicer fiducial scaling is a bit problematic for datasets with small voxel sizes

I’ve completely reworked markup scaling in latest nightly build (revision 28258). By default, markup size is set relative to the screen size (does not change if you zoom in/out in a view), in both 2D and 3D views. Therefore scale is always reasonable, regardless of the size or spacing of the volume. I’ve also added an option to specify absolute physical size - then the markup size remains physically the same, so it changes as you zoom in/out in a view.

---

_[View the full topic](https://discourse.slicer.org/t/support-for-aim-isq-files-generated-on-scanco-microct/6261)._
