wrote:
On 17/10/12 16:58, Eric Momsen wrote:
Hi all,
I'd like to do some further enhancements of i.segment (GSOC 2012
project, will hopefully send an official announcement soon!), and have
a chance to use it for a class homework project... if I include some
unit tests of the results
Sorry for not responding right away, I hadn't realized the code sprint
started (finished?!) already. There is a paper deadline this month and a
thesis to write that has consumed my attention... I don't think I'll have
time for anything in February. If noone else wants/needs to do it sooner,
I
Hi all,
I'd like to do some further enhancements of i.segment (GSOC 2012
project, will hopefully send an official announcement soon!), and have
a chance to use it for a class homework project... if I include some
unit tests of the results. I've previously used junit/Netbeans. For
GRASS
The short answer is yes, it will be difficult. The GRASS-internal
vector buffering algorithm has a number of bugs, the only vector
buffering method that is AFAICT bug-free is v.buffer in trunk with
GEOS support which uses the GEOS buffering algorithm which in turn
does not (yet?) support
On Thu, Sep 6, 2012 at 8:59 AM, Moritz Lennert mlenn...@club.worldonline.be
wrote:
On 06/09/12 15:44, Markus Neteler wrote:
Hi Eric,
great work with the i.segment, I just made a test with the NC Landsat
sample data:
i.segment -w -l group=lsat7_2000 output=testsegment threshold=4 \
Hi all,
Final GSoC report for this project... I'm behind on my reading and
didn't realize we would have a report for the final week.
I worked on code clean up and manual writing this week, so it is in
good shape for a final version that others can easily read. Image
segmentation is a big task,
usage.
Regards,
Eric
On Fri, Aug 3, 2012 at 5:39 PM, Eric Momsen eric.mom...@gmail.com wrote:
Happy Friday,
Here is this week's report:
Completed:
* Implemented starting seeds
* Added Manhattan distance as a user option
* Put iseg IDs back into SEG file to save RAM for large maps
* Added
Happy Friday,
Here is this week's report:
Completed:
* Implemented starting seeds
* Added Manhattan distance as a user option
* Put iseg IDs back into SEG file to save RAM for large maps
* Added Z-order (instead of row-major) processing order
Plans:
My original schedule called for a vacation
Hi all,
Here is the weekly report.
Completed:
* Finished 2 ToDo tasks that should have sped up the algorithm. One
was helpful, the other wasn't.
* Started implementing the feature to allow the user to give start
seeds for the segments.
* Started implementing a Z-order (instead of row major
TGIF!
Here is my report:
Completed:
Implemented the option to consider 8 or 4 pixel neighbors.
Fixed the boundary constraints option.
Cleaned up lots of small questions throughout the code.
Plan:
Same as last week, add as many of the top priority items as possible.
I will continue with
Hi,
Here is this week's update:
Accomplished:
* mid term review, not just the required question from Google, but
also compiling and prioritizing remaining ideas for improving the
program.
* Started on that todo list, doing some general code clean up after
getting some detailed comments from
Hi everyone,
Accomplished both planned tasks:
1. An optional size threshold, to force a final merge for very small
segments (even when not similar) makes very nice looking segments. (It
will be up to the user to decide if more cohesive segments are worth the
slight increase in heterogeneity.)
Hi,
As I suspected, I planned too much for the week. Progress was made in 2 of
the 3 tasks:
* Updated storage technique for some of the processing flags and
information. Big speed improvement, but still further gains are needed.
* Validation: No strict/formal validation was completed. But
aren't
considered spam? Let me know if I should hold back and only commit 1-2
times per week when more significant tasks are completed.
Have a good weekend,
Eric
-- Forwarded message --
From: Eric Momsen eric.mom...@gmail.com
Date: Fri, Jun 22, 2012 at 4:21 PM
Subject: Image
TGIF!
It is fun to be into the guts of the coding.
Completed:
* Segmentation will run on tiny maps, using arrays. This demonstrated
algorithm steps are sound, resulting segments were correct.
* Started to implement some linked lists to increase the size of the map
that can be processed.
Next
Hi!
Sorry for the day late report. I was pushing to have the basic algorithm
going, and wanted to report that it already works alas, it compiles,
but there is still some other bug or logic error I still need to find...
Completed:
* I/O works, the module can read imagery groups into
Hi all,
Completed:
I spent the week learning and implementing the segmentation library which
deals with tiling large rasters to balance memory constraints with disk
I/O. It is totally different from image segmentation, the task of the
program, so hopefully the dual meaning of the word won't
On Tue, May 29, 2012 at 5:08 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 28/05/12 06:14, Eric Momsen wrote:
On Sat, May 26, 2012 at 8:10 AM, Moritz Lennert
mlenn...@club.worldonline.be
mailto:mlennert@club.**worldonline.bemlenn...@club.worldonline.be
wrote
On Sat, May 26, 2012 at 8:10 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
[...]
[2]
https://trac.osgeo.org/grass/**browser/grass-addons/grass7/**
imagery/i.segmenthttps://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.segment
I've just added a series of comments
Follow up on some of the questions below.
Also, I posted a brief project report to the other mail list:
http://lists.osgeo.org/pipermail/soc/2012-May/001747.html
On Fri, May 25, 2012 at 3:47 AM, Markus Metz
markus.metz.gisw...@googlemail.com wrote:
On Thu, May 24, 2012 at 7:29 PM, Eric Momsen
Hi,
Thanks everyone for the nice greetings, I'm very impressed with how polite
and helpful the GRASS community is.
There is a wiki [1] and source code repository [2] for the Image
Segmentation - Google Summer of Code project.
The mentors for the project have already provided a lot of advice, if
On Tue, Apr 3, 2012 at 9:57 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
I personally am a bit weary of increasing dependencies between packages, but
at the same time, why re-invent the wheel. Integrating the OTB algorithms
into GRASS would definitely be a great plus.
This said,
conversation continued below...)
On Fri, Mar 23, 2012 at 5:47 PM, Wolf Bergenheim
wolf+gr...@bergenheim.net wrote:
On Fri, Mar 23, 2012 at 22:04, Eric Momsen eric.mom...@gmail.com wrote:
On Fri, Mar 23, 2012 at 2:41 PM, Wolf Bergenheim
wolf+gr...@bergenheim.net wrote:
Hi Eric!
It might help
Hi everyone,
I'm relatively new to the GRASS world, and thought I would send a
quick introduction. After spending some time in the real world as
an engineer, I have returned to university life and have a first goal
of a master's degree in computer science. My research currently
involves data
with
something, should I sketch the idea here first? Is someone available
to mentor?
-Eric
--Wolf
On Fri, Mar 23, 2012 at 20:14, Eric Momsen eric.mom...@gmail.com wrote:
Hi everyone,
I'm relatively new to the GRASS world, and thought I would send a
quick introduction. After spending some
25 matches
Mail list logo
