Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Peer Feedback for milestone 4 #62

Open
8 of 12 tasks
katieb1 opened this issue Mar 25, 2020 · 5 comments
Open
8 of 12 tasks

Peer Feedback for milestone 4 #62

katieb1 opened this issue Mar 25, 2020 · 5 comments
Milestone

Comments

@katieb1
Copy link
Collaborator

katieb1 commented Mar 25, 2020

Here are the actionable items for milestone 4 based on the peer feedback we received (UBC-MDS/software-review#15)

  • Note: I removed duplicate feedback from reviewers

Reviewer 1:

  • Documentation:

  • Remove k argument from tunnel_filter()

  • Fix any typos in examples (we should run the examples on our own computers to make sure they work)

  • Add example for colour_filters()

  • Add inline comments to function code

  • Either remove random images from root directory or move them to an images folder

  • Functionality:

  • Fix importation code (should be from pymagine import vignette_filter instead of from pymagine import pymagine etc.)

Reviewer 2:

  • Documentation:

  • Function names should be consistent (e.g. vignette_filter vs. colour_filters)

  • Functionality:

  • There is apparently a bug in the edge_detection filter where it is returning black images -> investigate this and see if it can be fixed

  • Remove shape values output from tunnel_filter

  • Index file name of saved images so that they don't overwrite each other (this will be useful if the user wants to input a list or array of images)

  • Print image directly with imshow() (I know we already tried this, but it might be worth revisiting if we should have an option to do this?)

  • Add a separate function argument for saving image to a folder

Now we should have a discussion of which tasks are necessary/plausible to include, and who will do each task.

@katieb1 katieb1 added this to the milestone-4 milestone Mar 25, 2020
@katieb1
Copy link
Collaborator Author

katieb1 commented Mar 25, 2020

The issues I can tackle:

  • Remove k argument from tunnel_filter
  • Remove images from root directory
  • Remove shape value output from tunnel_filter
  • Add function argument for saving image to a folder/naming the output image (this also fixes the indexing issue, since the user can specify the names of the images in a loop)

@Sukriti1312
Copy link
Collaborator

I can add example to colour_filters function

@brendoncampbell
Copy link
Collaborator

brendoncampbell commented Mar 26, 2020

I will:

  • fix the issue in my function example
  • consider a couple more code comments, but I have a decent number already

Questions/comments:

  • Agree function name consistency could be improved but not sure if its worth the hassle/risk at this point. Colour_filterS isn't the end of the world in my opinion because it actually contains a variety of effects, but for the edge detection I agree we could have included 'filter' somehow for consistency. Given the circumstances, I don't think its a huge deal and am fine to leave it
  • I'm not clear on the 'from pymagine import vignette_filter' item. As far as I can see this is the way it's already done? Am I missing something?
  • Don't really care to figure out the imshow() stuff at this stage given the issues we had, but agree that would be a nice improvement in the future

@katieb1
Copy link
Collaborator Author

katieb1 commented Mar 26, 2020

Sounds good!

I agree with the function name consistency - I feel like at this point it is more of a "cosmetic" thing and I think the other feedback is more useful to focus on right now.

As for the from pymagine import vignette_filter, I fixed that in my latest PR. The issue was that in our initial example, the import instructions were from pymagine import pymagine and it needed to be from pymagine import vignette_filter AND THEN when calling the function we needed to write vignette_filter.vignette_filter() rather than just calling vignette_filter() directly.

@trevorkwan
Copy link
Collaborator

trevorkwan commented Mar 26, 2020

I have fixed these issues:

"There is apparently a bug in the edge_detection filter where it is returning black images -> investigate this and see if it can be fixed"

"Add inline comments to function code"

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

No branches or pull requests

4 participants