[ome-devel] "Correct" procedure for defining instruments
Ilya Goldberg
igg at nih.gov
Thu Nov 18 14:42:13 GMT 2004
It doesn't matter at all if you import them during installation or
after.
We've committed ourselves to continuity of databases installed since
the OME 2.0 release, which means that future releases of the software
are supposed to update existing databases. So in practical terms, if
you import this instrument description at any point, it should stick
around through future releases of OME.
If you're doing a lot of development and you're changing your
instrument descriptions around and doing a lot of installations, it
might be worth-while to automate their import until this gets out of
the "development" phase. There is a manifest file (a file listing a
bunch of filenames) called src/xml/CoreXML which lists all the XML
files that get imported at the end of the installation process. You
can add your files to that list, and they will be imported by the
installer.
-Ilya
On Nov 18, 2004, at 3:11 AM, Richard Beare wrote:
> Hi,
>
> I'm wondering what the "right" way of going about the following is. We
> are probably going to be including images from 2 different microscopes
> in our OME installation.
>
> I'm reading the XML overview section about the instrument element.
>
> Is the appropriate approach to create a couple of xml files,
> instrumentA.xml and instrumentB.xml and import them after
> installation, or is it better to modify some files during
> configuration and allow the instrument descriptions to be created at
> installation time?
>
> Thanks
>
>
> --
> Richard Beare, CSIRO Mathematical & Information Sciences
> Locked Bag 17, North Ryde, NSW 1670, Australia
> Phone: +61-2-93253221 (GMT+~10hrs) Fax: +61-2-93253200
>
> Richard.Beare at csiro.au
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>
More information about the ome-devel
mailing list