Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm need to have 64-bit addressing, due to the size of my programs and especially data, but I have a Pentium 4 machine. Is it feasible to use a 64-bit distribution on a 32-bit machine, and if so, can anyone recommend one?
Thanks for the replies. I'm putting together a patient-specific neurosurgery simulator, based on image processing on CT and MR volumes that are resampled to consist of isotropic voxels, and these are very large volumes of data.
I developed this software up to now on smaller volumes (128 x 512 voxels x 512 voxels) that had the original CT sampling, which was not isotropic (.489mm x .489mm x 1mm), but some of what comes next requires isotropic spacing (.489mm x .489mm x .489mm), which entails a huge amount of data (254 x 512 x 512 voxels). If not for this, then I have to rewrite my code extensively, I believe. I can't use isotropic voxels that are more sparse, because some fine bone structures are not resolved well then.
Sounds like it's time to spend a few hundred bucks for a 64 bit machine. Better than re-writing code for 32bit - that's for sure. Keep up the great work!!
Originally posted by JapanMtlExpat Thanks for the replies. I'm putting together a patient-specific neurosurgery simulator, based on image processing on CT and MR volumes that are resampled to consist of isotropic voxels, and these are very large volumes of data.
I developed this software up to now on smaller volumes (128 x 512 voxels x 512 voxels) that had the original CT sampling, which was not isotropic (.489mm x .489mm x 1mm), but some of what comes next requires isotropic spacing (.489mm x .489mm x .489mm), which entails a huge amount of data (254 x 512 x 512 voxels). If not for this, then I have to rewrite my code extensively, I believe. I can't use isotropic voxels that are more sparse, because some fine bone structures are not resolved well then.
Cheers,
JME
WOW, I wonder how many words in here I did not understand... . Sorry for my ignorance... lol
CT is computed tomography, a method for producing an image volume of a patient that displays bone and soft tissues, as well as air.
MR is magnetic resonance, which produces image volumes of a patient that displays different soft tissues with different intensities: for a certain kind of imaging protocol, grey matter in the brain looks grey, white matter looks white, the cortico-spinal fluid looks dark, and so on.
In order to use the two sets of data together for my tissue classification, I have to register them (transform the MR data to CT space), then redo the sampling of MR data so that it conforms to CT sampling. In general, the CT sampling is dense along the x (left-right) and y (front-back) axes, but less dense along z (top-bottom), whereas for some of the processing that I'm doing, I have to have them with the same spacing between samples along all 3 axes: isotropic spacing. Resampling them increases the number of total points that I have to process, which means that I'm increasing the size of the CT volume, in terms of # of points, and likewise with the MR data, which reflects the sampling of the former.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.