Skip to content

Refactoring all project & adding two new operators top hat - #3

Open
edelgadoh wants to merge 2 commits into
fiji:masterfrom
edelgadoh:master
Open

Refactoring all project & adding two new operators top hat#3
edelgadoh wants to merge 2 commits into
fiji:masterfrom
edelgadoh:master

Conversation

@edelgadoh

Copy link
Copy Markdown

Hi all,

I did a refactoring in all the code. I created classes for each operator.
Finally I added two new operators "White Top Hat" & "Black Top Hat"

See you!

@ctrueden

Copy link
Copy Markdown
Member

@dprodanov What do you think?

@ctrueden

Copy link
Copy Markdown
Member

@edelgadoh Thanks. We'll see what Dimiter says about it.

I just wanted to point you also to the ImageJ Ops project, where the greater community is focusing these sorts of efforts. We haven't integrated grayscale morphology algorithms into Ops yet, but we definitely want to. See also imagej/imagej-ops#62

@edelgadoh

Copy link
Copy Markdown
Author

ok, thanks for the information about the other project, in my spare type I could help a little :)

@dprodanov

Copy link
Copy Markdown
Collaborator

I saw the message just now. My bad. Sorry.

@dprodanov

Copy link
Copy Markdown
Collaborator

The refactoring looks logical.

@ctrueden

Copy link
Copy Markdown
Member

Aahh, sorry @edelgadoh that this sat unmerged for so long!

@dprodanov How do you want to proceed? Do you want to maintain this component? I added you as a collaborator to this repository. Or are you too busy? Please see https://imagej.net/Team for info about the team roles for SciJava-, ImageJ- and Fiji-related projects.

@edelgadoh I know it has been over 3 years, but... do you still want to see this merged? If so, I can clean it up. Or if you don't care, we can just close it.

@dprodanov

Copy link
Copy Markdown
Collaborator

@ctrueden Hi Curtis,
Of course, I can maintain the component. The code is pretty stable but I can add testing cases.

@edelgadoh

Copy link
Copy Markdown
Author

@ctrueden Hi!

yeah, it was three years ago hehehe, I just watch this conflicts, I'm going to resolve this.

@edelgadoh

Copy link
Copy Markdown
Author

I can't do anything :( "This branch has conflicts that must be resolved
Only those with write access to this repository can merge pull requests."

@dscho

dscho commented Sep 12, 2019

Copy link
Copy Markdown
Contributor

This branch has conflicts that must be resolved

@edelgadoh why not do that? Just click on the link " Use the command line to resolve conflicts before continuing." below to see detailed instructions how to do that.

@dprodanov dprodanov left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not delete files.

@edelgadoh edelgadoh left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

basically I renamed a class and separated a big class in many classes

@edelgadoh

Copy link
Copy Markdown
Author

@dscho @dprodanov is there anything to do? or is it already ok?

@dprodanov

dprodanov commented Jan 12, 2020

Copy link
Copy Markdown
Collaborator

Have you tested the code? I see that it compiles but there is a conflict in MorphoProcessor (see below).

@dscho

dscho commented Jan 12, 2020

Copy link
Copy Markdown
Contributor

@edelgadoh even if @dprodanov did not say it, it would be better to use git rebase to rebase your changes on top of the current tip of master, i.e. git rebase b25846ecd933f5a6e88a234668e065f5c99b6a90 (you might need to git fetch https://github.com/fiji/Gray_Morphology/ master first).

@dprodanov I see you still stick to your terse replies, terse to the point of not exactly being helpful... I kind of hoped that several Google Summer of Code seasons would have helped you develop some mentoring skills, but I see that there is still quite some room for improvement. Having said that, I still think you have the capability to learn that. I told you back when I was still active in the Fiji project, and I tell you now: you got it in you. Discover that mentor in you!

@dprodanov

dprodanov commented Jan 12, 2020 via email

Copy link
Copy Markdown
Collaborator

@edelgadoh

Copy link
Copy Markdown
Author

@dscho @dprodanov I just did the rebase with the master, it compiles and I already tested the generated JAR in the last version of ImageJ, It works! ... the two operators that I added worked too.

@fiji fiji deleted a comment from dscho Jan 13, 2020
@dprodanov

Copy link
Copy Markdown
Collaborator

Hi Edwin,
I ran your code but I can't reproduce the result from the (my) reference implementation. Opening with 4 and 8 circular SEs. Please see the images for reference. Note that they are converted to JPG so bitwise operations will be biased.
blobs_open4
blobs_open8

Dimiter

@dprodanov

Copy link
Copy Markdown
Collaborator

Dear @edelgadoh,

did you look at the images?

best regards,

Dimiter

@edelgadoh

Copy link
Copy Markdown
Author

Hi @dprodanov , I downloaded your images and compared with the JAR generated from your master branch https://github.com/fiji/Gray_Morphology and also with the JAR generated with the last commit from my fork https://github.com/edelgadoh/Gray_Morphology (and the current PR) and the images were identical. I used the ImageJ software to do a difference between each of this images and the result was an empty image, all pixels with zero value.

I used the open operator with circular SE 4 and then changing with circular SE 8

blobs-se8-comment-github
blobs-se8-comment-github

blobs-se8-branch-master
blobs-se8-branch-master

blobs-se8-branch-forked
blobs-se8-branch-forked

blobs-se8-jar-downloaded
blobs-se8-jar-downloaded

blobs-se4-jar-downloaded
blobs-se4-jar-downloaded

blobs-se4-comment-github
blobs-se4-comment-github

blobs-se4-branch-master
blobs-se4-branch-master

blobs-se4-branch-forked
blobs-se4-branch-forked

@edelgadoh

Copy link
Copy Markdown
Author

I didn't find the difference, remember that I did a rebase with master and I only moved code, I didn't change any behavior. Basically I separated a big class in many classes and I added two operators.
image

@edelgadoh
edelgadoh requested a review from dprodanov January 29, 2020 00:12
@edelgadoh

Copy link
Copy Markdown
Author

@dprodanov is there something I can do to continue with it? ... I didn't find any difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants