RSS/Atom feed Twitter
Site is read-only, email is disabled

gsoc project

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

7 of 7 messages available
Toggle history

Please log in to manage your subscriptions.

gsoc project rafael mesquita 19 Mar 00:01
  gsoc project Bill Skaggs 19 Mar 05:32
  gsoc project Sven Neumann 19 Mar 08:20
  gsoc project Ingo Lütkebohle 19 Mar 10:45
   gsoc project rafael mesquita 19 Mar 23:53
    gsoc project Bill Skaggs 20 Mar 00:23
  gsoc project Øyvind Kolås 20 Mar 19:07
rafael mesquita
2008-03-19 00:01:56 UTC (about 17 years ago)

gsoc project

Hi everyone,
My name is Rafael, I am an Brazilian student of Computer Engineering from Universidade de Pernambuco and about one year ago i have been studying image processing, so i become interested in working in an gimp project. People usually want to process image for specifics reasons : noise extractions, signatures analysis, historic documents analysis, activation areas detection from an human brain studies, and for so many other reasons. In addition to this, those images can be of n different types. My general idea is to make a plugin to help people doing new Filters, for their specific reasons, without the need of writing new code. The idea consists on creating those filters from basic Morphologic Operators (dilate, erode, opening, closing and morphological gradient) and , in the future, creating new filters based on other filters (combining them). I know that gimp already works with Dilate and Erode operations, but it does not give the possibility of creating new structuring elements for those operands (dilating an image with a cross 13x13 can be much better than doing it with a circle 3x3, depending on the user´s need) and neither of combining them with other operations. There is something similar to what i want to do, in an ImageJ Plugin (

http://svg.dmi.unict.it/iplab/imagej/Plugins/Morphological%20Operators/Morphological%20Operators/MorphologicalOperatorsPlugin.htm- here you can see an image from the interface of Morphological Operators
plugin that can help you to understand my idea). I usually work with this tool and i think it is very useful, but it can`t save operators made by user to combine them with other operations in the future.

Well, i am waiting a feedback from you. Suggestions/Critics ? is this idea interesting/relevant for gimp ?

you can found me on #gimp -> Galva and msn -> rgalvaomesquita@msn.com.

Thank you very much for your attention :),

Rafael

Bill Skaggs
2008-03-19 05:32:51 UTC (about 17 years ago)

gsoc project

rafael mesquita wrote:

Hi everyone,
My name is Rafael, I am an Brazilian student of Computer Engineering from Universidade de Pernambuco and about one year ago i have been studying image processing, so i become interested in working in an gimp project. [...]

Hi Rafael, thanks for introducing yourself. Your ideas are quite sophisticated, but I don't have a clear picture of who would use this capability, or what they would use it to do. Could you explain a little more, please?

-- Bill

Sven Neumann
2008-03-19 08:20:46 UTC (about 17 years ago)

gsoc project

Hi,

this sounds like an interesting project, but it is very much directed towards scientific image processing which seems quite out-of-scope for GIMP. Of course such a plug-in could be written and it would be a nice addition for a very special and very small user group. But I don't think it would be of interest for our main user base. Of course, if we can find a mentor for it, it could still be a GSoC project. I don't think it would get high priority though.

Sven

Ingo Lütkebohle
2008-03-19 10:45:30 UTC (about 17 years ago)

gsoc project

Hi Rafael,

your idea sounds interesting, and would definitely be a great tool for ImageJ, but I'm not sure it is very relevant for The GIMP, which is mainly targeted at interactive image manipulation, as opposed to the batch processing one usually does in image processing applications of the sort you describe.

If you are currently using ImageJ, what would you say is the advantage of doing it in The GIMP, instead of a GUI on top of ImageJ? ImageJ has all the relevant operations already, so I would expect that to be much less work.

cheers,

On Wed, Mar 19, 2008 at 12:01 AM, rafael mesquita wrote:

People usually want to process image for specifics reasons : noise extractions, signatures analysis, historic documents analysis, activation areas detection from an human brain studies, and for so many other reasons.

cheers, Ingo

rafael mesquita
2008-03-19 23:53:12 UTC (about 17 years ago)

gsoc project

Bill ,
like Sven said, my idea is directed towards scientific image processing, but I think this doesn`t mean only few people would use it, maybe this could help gimp developer`s too, for example.

Sven, I understand your point, and agree with most things that you said.

Ingo, it really would be much less work, but the work would not be only doing a GUI for imageJ. the advantage of doing it on The Gimp is that The Gimp is a much bigger project, than imageJ and it could have those interesting tools.

Well, If you change your mind and decide to go ahead with this, or any similar idea, please contact me, i am disposed to talk.

thank you for your attention, again

2008/3/19, Ingo Lütkebohle :

Hi Rafael,

your idea sounds interesting, and would definitely be a great tool for ImageJ, but I'm not sure it is very relevant for The GIMP, which is mainly targeted at interactive image manipulation, as opposed to the batch processing one usually does in image processing applications of the sort you describe.

If you are currently using ImageJ, what would you say is the advantage of doing it in The GIMP, instead of a GUI on top of ImageJ? ImageJ has all the relevant operations already, so I would expect that to be much less work.

cheers,

On Wed, Mar 19, 2008 at 12:01 AM, rafael mesquita wrote:

People usually want to process image for specifics reasons : noise extractions, signatures analysis, historic documents analysis,

activation

areas detection from an human brain studies, and for so many other

reasons.

cheers, Ingo

-- Dipl.-Inform. Ingo Lütkebohle
Faculty of Technology
Bielefeld University
http://www.techfak.uni-bielefeld.de/~iluetkeb/

Fingerprint 3187 4DEC 47E6 1B1E 6F4F 57D4 CD90 C164 34AD CE5B

Bill Skaggs
2008-03-20 00:23:44 UTC (about 17 years ago)

gsoc project

rafael mesquita wrote:

Well, If you change your mind and decide to go ahead with this, or any similar idea, please contact me, i am disposed to talk.

That isn't quite how GSOC works. Students apply, then people from the project rank their proposals. Google looks at the rankings and decides which projects to support. We're just letting you know that some of us are not disposed to give such a project a very high ranking unless you can do more to convince us that the results would be used by numerous people to do important things.

Best wishes,

-- Bill

Øyvind Kolås
2008-03-20 19:07:22 UTC (about 17 years ago)

gsoc project

On Tue, Mar 18, 2008 at 11:01 PM, rafael mesquita wrote:

My name is Rafael, I am an Brazilian student of Computer Engineering from Universidade de Pernambuco and about one year ago i have been studying image processing, so i become interested in working in an gimp project. People usually want to process image for specifics reasons : noise extractions, signatures analysis, historic documents analysis, activation areas detection from an human brain studies, and for so many other reasons. In addition to this, those images can be of n different types. My general idea is to make a plugin to help people doing new Filters, for their specific reasons, without the need of writing new code. The idea consists on creating those filters from basic Morphologic Operators (dilate, erode, opening, closing and morphological gradient) and , in the future, creating new filters based on other filters (combining them).

If the goal is to write filters suitable for scientific processing I would think it makes sense
to implement the filters for GEGL instead of GIMP, since GEGL operates with 32bit floating
point buffers. Combining operations in GEGL to create new combined ops is something that already is possible, but needs further work (it is currently hard-coded in C while it should be done using an XML based format or similar (as well as have a usable UI.).

/Øyvind K. (responding from somewhere near Shopping Recife)