Re: [odin-devel] RE: Seq Compile/Link Problem

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thies Jochimsen wrote:
<blockquote cite="mid...@jo..." type="cite">
 <pre wrap="">I just checked: Under platforms/IDEA_n4/Ice in the odin directory
tree, there should be the files
IceOdin.cpp IceOdin.h MakeDebug.X86 MakeRelease.X86
necessary to build the reco on the scanner. Please let me know
if you still can't find them, and what you see instead in this location.
 </pre>
</blockquote>
For some reason, my lazy brain told me install.idea would take care of
that. Sorry, you're right. 
 
I was able to make the IceOdin.DLL with the following steps: 
* copied sources and make files to the IceProgram directory. In my
case: V:\n4\pkg\MrServers\MrIcePrograms\IceOdin 
* commented out the pre VA25 includes at the beginning of IceOdin.cpp
and IceOdin.h 
* Modified MakeDebug.X86 and MakeRelease.X86 to fit VA25 (Just a note
that the make files in the CVS is for VA23.) 
* then I can build with makeIcePrg 
* works great on the scanner (Allegra) 
 
Have some problem with reco under debian though, will report that back
in another email. 
<blockquote cite="mid...@jo..." type="cite">
 <pre wrap=""></pre>
 <pre wrap="">My 0.02$: It would be too ambitous to try to replace the product
sequences/applications on each platform for the everyday radiologist.
Instead, Odin focuses on the MR researcher who wants to try things
quickly, independent of the platform and with the possibilty to simulate
the whole process. For example, I'm currently developing/testing the
GRAPPA reconstruction using a synthetic MR signal generated by
ODIN. And because the simulator as a virtual platform is on equal
footing with the other platforms, it is very likely that this will work on
the actual scanners 'out of the box'.
I think this orthogonality (the sequences/reconstruction on one axis
and the platforms on the other axis) is the mayor strength of Odin.
Thus, instead of competing with native stuff from each vendor, I see
Odin as a supplement available to the MR researcher.
 </pre>
</blockquote>
Totally agree. Thanks for the clarification. Now I'm clearer of the
goal of ODIN. 
 
<blockquote cite="mid...@jo..." type="cite">
 <pre wrap="">I'm not sure what you mean by features of the native environment.
Are you, for example, thinking about something like real-time support?
Instead of using a quick hack to support this on a certain platform,
I would rather want to add this feature in a general way, for example
by a trigger object in the sequence and an additional member function
of the sequence class where you can change the sequence 'on the fly'
depending on the MR signal just acquired. I think this would be a
portable way to add this feature on platforms which support real-time 
feedback. However, in the past, I made good experience with the strategy
'Add something only if you really need it'
so I'm hesitant to add new features 'in stock' because extra code
means extra maintenance, testing, etc.
But I'm certainly interested in which features you're specifically missing...</pre>
</blockquote>
Yes, I'm thinking about the feedback support. But not as far as
RealTime feedback based on MR signal (that certainly would be super
nice though). The most important thing missing for me right now is the:
physiological trigger support (i.e. Physio Card in IDEA, which is
standard on all the sequences). I'm not sure how easy is to add it
cross-platform, but a general trigger object will certainly make a lot
of cardiac people happy. Btw, the ability to control the phase
resolution was also missing in IDEA. 
 
<blockquote cite="mid...@jo..." type="cite">
 <pre wrap="">You are already doing a great job by reporting errors, problems and
giving feedback. If you want to learn more about the internals:
Read the publications on Odin (provided on the home page)
and read the draft tutorial (which is under development) by
changing to the directoy docs/tutorials and doing a 'make main.pdf'
(youl'll need the gs-common and tetex-* packages on Debian for this).
The generated main.pdf is short tutorial for an FSE sequence.
Also, you could look at the code of one of the basic sequence objects,
e.g. SeqAcq or SeqPuls (in odinseq/seqacq.* or odinseq/seqpuls.*)
and look at their corresponding drivers for IDEA in 
platforms/IDEA_n4/odinseq_idea/seqacq_idea.*
and
platforms/IDEA_n4/odinseq_idea/seqpuls_idea.*
how everything works together.
 </pre>
</blockquote>
Thanks for the pointer. Cracking down IDEA certainly sounds like a good
start. 
 
<blockquote cite="mid...@jo..." type="cite">
 <pre wrap="">Unfortunately, I have no idea how sequence programming works
on Varian. Do you have, similar to Bruker, a procedural 'pulse program'
in some custom language to be executed by the scanner?
If so, look at the code mentioned, alternatively at the Bruker/Paravision 
drivers under
platforms/Paravision/odinseq_paravision/seqacq_paravision.*
and
platforms/Paravision/odinseq_paravision/seqpuls_paravision.*
to get a feeling what has to be done.
 </pre>
</blockquote>
In Varian, there's a command "seqgen" which compiles the c code and
links it. It is loaded during run time. There's a set of Varian
statements for delay, gradient, etc.. that can be used to write the
source code. I'll take a look at your suggestions, read the Varian
manual and report back next week. 
 
<blockquote cite="mid...@jo..." type="cite">
 <pre wrap="">I would be happy to gain a new developer for Odin ;-)
If you are ready, I can add you as a developer to the Odin project,
you'll need a sourceforge account for this.
To add a new platform for Varian, I suggest add the drivers of a template 
platform with documentation what each class/function is supposed
to do. You could then copy this code and add the Varian-specific
stuff...

Thies</pre>
</blockquote>
I will let you know when I'm ready to be an odin developer. Thanks 
 
Gordon 
</body>
</html>

Re: [odin-devel] RE: Seq Compile/Link Problem

develop, simulate and run magnetic resonance sequences

Re: [odin-devel] RE: Seq Compile/Link Problem