[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-hackers] Re: submission of spatter - savannah.nongnu.org
From: |
Mathieu Roy |
Subject: |
[Savannah-hackers] Re: submission of spatter - savannah.nongnu.org |
Date: |
10 Sep 2003 09:58:00 +0200 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 |
Hi,
I'm evaluating the project you submitted for approval in Savannah.
address@hidden said:
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
>
> Alan Grosskurth <address@hidden> described the package as follows:
> License: gpl
> Other License:
> Package: spatter
> System name: spatter
> Type: non-GNU
>
> Description:
> Spatter is a set of command-line tools for the image analysis of cDNA
>
> microarrays. Given a set of image files and the array geometry,
>
> Spatter allows gridding, segmentation, and data extraction to be
>
> performed in a fully-automated manner. Spatter produces results for
>
> each step in the form tab-delimited text files, but can also generate
>
> visual representations of gridding and segmentation results in the
>
> form of image files.
>
> Spatter is implemented in C++ and Python. It is written in a modular
>
> style, in order to allow the different steps of the image analysis
>
> system to be modified or extended.
>
> The purpose of Spatter is to provide a highly accurate and
>
> fully-automated image analysis tool for cDNA microarrays.
>
> Currently, the modules for gridding and segmentation are finished, but
>
> the module for data extraction is not.
>
> Spatter is available at:
>
> http://www.cdf.toronto.edu/~g1gros/research/spatter/download/spatter-0.4.0.tar.bz2
In order to release your project properly and unambiguously
under the GPL, please place copyright notices and permission-to-copy
statements at the beginning of every file of source code.
In addition, if you haven't already, please copy a copy of the plain
text version of the GPL, available from
(http://www.gnu.org/licenses/gpl.txt), into a file named "COPYING".
Additional instructions are available from
http://www.gnu.org/licenses/gpl-howto.html.
The GPL FAQ explains why these procedures must be followed. To learn
why a copy of the GPL must be included with every copy of the code,
for example, go to
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude
Please register your project once more with the changes
mentioned above.
We cannot track projects that have been answered but not approved, so
we must ask you to register the project whenever you change the
registration. Make sure to apply all changes so you need to reregister
only once.
The re-registration URL found in our acknowledgement of your earlier
registration will direct you to the proper location.
Regards,
--
Mathieu Roy
Homepage:
http://yeupou.coleumes.org
Not a native english speaker:
http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english