> Cameron Huddlestone-Holmes: > |Hello DX users, > | > |I am working with a large dataset generated by high-resolution CT scans. It > |consists of 918 slices @ 1024x1024, 16-bit (~1.7Gb). Obviously this causes > |huge problems with memory, so I was hoping to make subsets of the data to > |regions of interest using the include module. > > You might want to consider using Slab instead of Include. > > > You're running on SGI, so another thought might be to build a 64-bit DX > (configure --with-large-arenas in CVS) which will get you > ~1.5GB total > data (e.g. 7GB), but won't remove the 2GB limitation on individual objects. > I haven't gotten back to chasing down the UI bugs, but the executive seemed > pretty sound. You might be able to connect a 32-bit dxui front-end to a > 64-bit dxexec back-end using the standard Connection->Start Server... but I > haven't tried it. Let me know if you want more info. > > > Randy Could you please explain what you mean by the "2Gb limitation on individual objects"? Is this a hard limit in dx's coding? If my original data file is a regular grid and under but close 2Gb, and I am only slabbing/including for example, will dx be creating any bigger objects?
I assume you can avoid the UI bugs in the 64-bit version if you run dx in script mode? Regards, Cameron
