Text archives Help
- From: Francis Burton <F.L.Burton@udcf.gla.ac.uk>
- To: Michael Callahan <callahan@sci.utah.edu>
- Cc: scirun-users@sci.utah.edu
- Subject: Re: [SCIRUN-USERS] Command line tools as modules?
- Date: Sat, 18 Sep 2004 15:51:03 +0100
Hi Michael - I appreciate your help.
At 12:53 17/09/04 -0600, Michael Callahan <callahan@sci.utah.edu> wrote:
>
There is no simple wrapper to do this at the moment. In order to make
>
it work you would have to write some SCIRun code for the modules.
>
Basically you will need to convert the data from whichever SCIRun format
>
is used into which format you are using, then call your functions, then
>
convert back. If you want to wrap your executables you could do that by
>
dumping the SCIRun data out to a temporary file, then invoking
>
sci_system to run your executable, then reading the data back in.
Even though there would be a performance hit, that sounds like a very
reasonable first step. Is sci_system part of a module? I couldn't find
it in any of the online documentation.
>
What data format are your standalone executables needing? We may
>
already have the converters in which case the wrappers would not be
>
terribly difficult to write.
Just numeric ascii data in columns, separated by spaces.
I should say that my main interest, at the moment, is using SCIRun to
provide a nice graphical front-end for the existing C program 'modules'
as an alternative to cobbling together shell scripts for novice users.
Francis
===========================================================================
== The SCIRun Users mailing list: send email to majordomo@sci.utah.edu ==
== for more details. ==
== Please acknowledge use of SCIRun in your papers and reports: ==
== see
http://software.sci.utah.edu/scirun-biopse_citation.bib ==
===========================================================================
Archive powered by MHonArc 2.6.16.