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

Stop using reference IDs and use reference names instead #217

Merged
merged 1 commit into from
Apr 22, 2014

Conversation

nealsid
Copy link

@nealsid nealsid commented Apr 18, 2014

I have a few more tests to fix but this is definitely ready for more eyeballs on it. Hopefully I'll be able to fix the remaining ones tomorrow.

@AmplabJenkins
Copy link

Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/280/

*/
recordNames.keys.filter(!dict.recordNames.contains(_)).foreach {
recordNames.keys.foreach {
Copy link
Member

Choose a reason for hiding this comment

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

It seems like we should be able to make this into a map/flatMap and to make val assign into an immutable data structure. Is there a reason it needs to be mutable?

Also, I'd prefer to change the name of the val assign to something different, as I feel that assign hash collides...

Copy link
Author

Choose a reason for hiding this comment

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

I think we can just rely on the overloaded ++ method, since our merge semantics are the same as what Scala provides for Maps. What do you think?

Copy link
Member

Choose a reason for hiding this comment

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

Good call! I think that'd be a clean implementation.

Neal notifications@github.com wrote:

  */
  • recordNames.keys.filter(!dict.recordNames.contains(_)).foreach {
  • recordNames.keys.foreach {

I think we can just rely on the overloaded ++ method, since our merge semantics are the same as what Scala provides for Maps. What do you think?


Reply to this email directly or view it on GitHub:
https://github.com/bigdatagenomics/adam/pull/217/files#r11774102

In adam-core/src/main/scala/org/bdgenomics/adam/models/SequenceDictionary.scala:

>       */
> -    recordNames.keys.filter(!dict.recordNames.contains(_)).foreach {
> +    recordNames.keys.foreach {

I think we can just rely on the overloaded ++ method, since our merge semantics are the same as what Scala provides for Maps. What do you think?


Reply to this email directly or view it on GitHub.

@fnothaft
Copy link
Member

Thanks for putting this together @nealsid! This looks great; I had a few small comments inline. I look forward to the finishing tests, and having this merged in.

@nealsid
Copy link
Author

nealsid commented Apr 18, 2014

Thanks for the comments, Frank!

@AmplabJenkins
Copy link

Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/282/

@AmplabJenkins
Copy link

Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/283/

@AmplabJenkins
Copy link

Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/284/

@AmplabJenkins
Copy link

Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/288/

@AmplabJenkins
Copy link

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/293/

@nealsid
Copy link
Author

nealsid commented Apr 22, 2014

Jenkins, test this please.

@AmplabJenkins
Copy link

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/294/

@nealsid
Copy link
Author

nealsid commented Apr 22, 2014

Ready for merging! Thanks @massie, @fnothaft

@nealsid
Copy link
Author

nealsid commented Apr 22, 2014

Oops, actually hold off. I'll rebase & squash.

@nealsid
Copy link
Author

nealsid commented Apr 22, 2014

Jenkins, test this place

@nealsid
Copy link
Author

nealsid commented Apr 22, 2014

Jenkins, test this please.

@AmplabJenkins
Copy link

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/295/

We decided that using RefSeq names for our contigs was better practice
than minting our own IDs and handling complicated sequence dictionary
merges.
@AmplabJenkins
Copy link

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/296/

@nealsid
Copy link
Author

nealsid commented Apr 22, 2014

This is good to go now. Thanks!

fnothaft added a commit that referenced this pull request Apr 22, 2014
Stop using reference IDs and use reference names instead
@fnothaft fnothaft merged commit b777945 into bigdatagenomics:master Apr 22, 2014
@fnothaft
Copy link
Member

Merged! Thanks @nealsid!

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.

3 participants