[Insight-users] Re: Morphological Top Hat & Contributions to the INSIGHT JOURNAL

[Luis Ibanez]

Hi Rupert,

Small contributions are welcome to the Insight Journal too.

The focus of the Journal is a very pragmatic one.

The rule of thumb for submission is:

    "Did you find your own code useful in your work ?"

if the answer is "yes",
then chances are that it will be useful for other readers too,
and therefore it is worth of being published in the journal
and shared with the community.

This is a Journal oriented to help developers get their job done.
It is not the typical Journal dedicated to make points for your
CV and your next promotion, or for the vanity of adding more
publications for the annual Lab report.

A new iterator certainly falls in the range of a valid and useful
submission. Iterators are a central piece of image processing
algorithms. In some cases, for example in the DanielssonDistance
map, and in the RegionGrowing algorithms, most of the complexity
of the algorithm is encoded in the iterators.

It is actually deceiving to find in many image processing text books
that they skip and disregard the complexity of visiting all the pixels
in an image. Few text books describe the performance trade-offs of
dealing with boundaries for neighborhood operations....


In the worst case scenario, if you submit something that people
don't find useful, what will happened is that you paper will not
receive any comments, and still in that case, we should wonder
if this happens because the importance of your contribution is
not understood at the moment of your submission..., so the judgment
should be delayed until some months have passed.  This is one of
the arguments for having continuous and permanent reviews in the
Insight Journal. You can always add one review to any paper in the
Journal, no matter when the paper was submitted.


   Regards,


      Luis


--------------------
Rupert Brooks wrote:
> I have experienced this problem submitting code as well.  The
> insight-journal approach sounds great, but i wonder if its
> appropriate for all code submissions.  Specifically, a while ago i
> submitted a new iterator class.  Its a pretty small contribution, 
> but we have to start somewhere, right :-)  If i submit that to Insight
> Journal it would barely merit a page.
> 
> So - should small things like that be submitted through the journal method
> or by some other means?  Is there a plan to add a separate "channel" in
> Insight Journal for these things?  Or should i just skip it and wait till i
> have a large collection of
> code to submit.
> 
> Anyways, I'm not trying to be critical, but supportive - i think the
> Insight Journal approach is excellent, just want to know how 
> best to get on board.
> 
> Cheers
> Rupert B.
> 
> Gaetan wrote:
> 
> 
>>>Luis, do you want to add those filters and their tests in ITK?
>>>Contributing to ITK is a pain: it's very hard to find help and nobody
> 
> reply
> 
>>>when contributions are sent. Why not take some time to reply to
> 
> contributors
> 
>>>as you do for users on this list ?
> 
> 
> Luis replied:
> 
>>The process for contributing code to ITK is almost
>>ready to be streamlined through the Insight Journal
>>http://www.insightsoftwareconsortium.org/InsightJournal/
> 
> 
> --------------------------------------------------------------------------------------
> Rupert Brooks                                     For every complex question
> rbrooks at cyberus.ca                            there is a simple and wrong solution
> www.cyberus.ca/~rbrooks                     --A. Einstein
> 
> 
> 
> Sent using cyberus.ca WebMail - http://www.cyberus.ca/
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
> 
>