Skip to content

[MISC] Alignment: aminoacid scoring scheme - lower case member constants #2599

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

Conversation

Irallia
Copy link
Contributor

@Irallia Irallia commented May 4, 2021

@vercel
Copy link

vercel bot commented May 4, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/seqan/seqan3/D173vmSyixxGMnKQ9EQAHzfG1fxy
✅ Preview: https://seqan3-git-fork-irallia-misc-alignmentaminoacids-6b3a04.vercel.app

@codecov
Copy link

codecov bot commented May 4, 2021

Codecov Report

Merging #2599 (a4eb444) into master (cca92c4) will not change coverage.
The diff coverage is 100.00%.

❗ Current head a4eb444 differs from pull request most recent head 40d62c7. Consider uploading reports for the commit 40d62c7 to get more accurate results
Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2599   +/-   ##
=======================================
  Coverage   98.27%   98.27%           
=======================================
  Files         273      273           
  Lines       10795    10795           
=======================================
  Hits        10609    10609           
  Misses        186      186           
Impacted Files Coverage Δ
...an3/alignment/scoring/aminoacid_scoring_scheme.hpp 88.23% <100.00%> (ø)
test/include/seqan3/test/tmp_directory.hpp 100.00% <0.00%> (ø)
include/seqan3/utility/views/type_reduce.hpp
include/seqan3/range/views/type_reduce.hpp 100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cca92c4...40d62c7. Read the comment docs.

@marehr marehr requested review from a team and SGSSGene and removed request for a team May 4, 2021 15:14
CHANGELOG.md Outdated
#### Alignment

* The member constants of `seqan3::aminoacid_similarity_matrix` were changed to lower case
([\#....](https://github.com/seqan/seqan3/pull/....)):
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Suggested change
([\#....](https://github.com/seqan/seqan3/pull/....)):
([\#2599](https://github.com/seqan/seqan3/pull/2599)):

Copy link
Contributor

Choose a reason for hiding this comment

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

I am confused by this suggestion. Arn't you the author and should add this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, I marked it for me to make the change when I received your review. Sorry for the confusion.

CHANGELOG.md Outdated
#### Alignment

* The member constants of `seqan3::aminoacid_similarity_matrix` were changed to lower case
([\#....](https://github.com/seqan/seqan3/pull/....)):
Copy link
Contributor

Choose a reason for hiding this comment

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

I am confused by this suggestion. Arn't you the author and should add this change?

@@ -28,33 +28,39 @@ namespace seqan3
*
* This enum provides IDs for amino acid similarity matrixes of the
* [BLOSUM](https://en.wikipedia.org/wiki/BLOSUM) and [PAM](https://en.wikipedia.org/wiki/Point_accepted_mutation)
* families.
* families (last access 04.05.2021).
Copy link
Contributor

Choose a reason for hiding this comment

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

I like this!

Copy link
Member

Choose a reason for hiding this comment

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

I'm not a big fan of this (in this context, having a bibliography is something else :)):

  • No one will ever update the dates even if they check the links
  • We don't use any information from the links, it's just some \seealso basically
  • Access dates are implicitly stored in the git history

Copy link
Member

Choose a reason for hiding this comment

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

Agree with @eseiler; if we can somehow automatically add that date I would love that, but manual management isn't feasible.

Copy link
Contributor Author

@Irallia Irallia May 7, 2021

Choose a reason for hiding this comment

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

I'm okay with undoing it. I just want to point out that I had discussed and started this in another PR with @smehringer and @MitraDarja.
-> #2290 (comment)

Why do you think you do not update this date when you edit the documentation for it?
And wouldn't an automatic check be error-prone? Then one checks only whether the page is there, but not whether it still contains what we have taken over or to which we want to refer?

EDIT: or do you especially mean this link?

Copy link
Contributor

Choose a reason for hiding this comment

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

The "last access" only has to be updated if the enum provided IDs on wikipedia change. Isn't this very helpful? One could just look at the wikipedia diff from 04.05.2021 until today and see if anything has changed.

Copy link
Member

@eseiler eseiler May 7, 2021

Choose a reason for hiding this comment

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

The "last access" only has to be updated if the enum provided IDs on wikipedia change. Isn't this very helpful? One could just look at the wikipedia diff from 04.05.2021 until today and see if anything has changed.

But the IDs come from some paper, it's not an invention of Wikipedia. The papers won't change and to check for some change would require you to manually look into it. I don't see this happen.

If it's not automatic, it's not reliable (include order, first brief or author, | at end or beginning of lines, how are lambdas indented, are the used URLs at all valid?).

Why do you think you do not update this date when you edit the documentation for it?

Easy to overlook if I don't even touch text in vicinity of the URL; then you would rely on someone else to know that there are links and verify them. And we have quite a few of them....

It would be nice to have, but it is also something that is quite useless if not carefully curated.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I understand the objection, but I would trust us that one gets into the habit of looking for such links. But I have no strong feelings and have undone it.

Copy link
Contributor

Choose a reason for hiding this comment

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

So if I understand correctly, your objection is actually against citing Wikipedia and rather cite the original paper?

@Irallia Irallia force-pushed the misc/alignment/aminoacid_scoring_scheme_lower_case_member_constants branch from 604e198 to a4eb444 Compare May 7, 2021 10:08
@Irallia Irallia requested a review from SGSSGene May 7, 2021 11:07
@Irallia Irallia requested review from a team and marehr and removed request for a team May 10, 2021 10:03
@@ -20,7 +20,7 @@ index ef141a7e9..7b0927215 100644
- seqan3::align_cfg::method_global,
Copy link
Member

Choose a reason for hiding this comment

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

please don't change patches, if they don't work they need to be changed differently :)

Copy link
Member

@marehr marehr left a comment

Choose a reason for hiding this comment

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

nearly done, api stability patches shouldn't be changed :)

@Irallia Irallia force-pushed the misc/alignment/aminoacid_scoring_scheme_lower_case_member_constants branch from a4eb444 to 40d62c7 Compare May 10, 2021 10:39
@marehr marehr self-requested a review May 10, 2021 11:30
@marehr marehr merged commit f891e79 into seqan:master May 10, 2021
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.

aminoacid_scoring_scheme: lower case member constants
4 participants