Skip to content
This repository has been archived by the owner on Oct 8, 2019. It is now read-only.

Mainly entailed incorporating the new thrift API #78

Merged
merged 1 commit into from
Jul 13, 2012

Conversation

danhammer
Copy link
Contributor

Updated forma.logistic.classify and forma.ops.classify to reflect new thrift API.
... Merging in specific namespaces from feature/deliver.

(defn unpack-feature-vec [val neighbor-val]
(defn unpack-feature-vec [forma-val neighbor-val]
"TODO: Convert forma-val to thrift - see forma-seq
(schema/unpack-forma-val forma-val)"
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this right? Don't we want (thrift/unpack forma-val) instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

you are right. but this is in the comment. it will be taken out.

Copy link
Contributor

Choose a reason for hiding this comment

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

This is just in the doc. Dan removes it in another pull request he's working on.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, may have misinterpreted what you wrote. If you mean that the whole function unpack-feature-vec should be in thrift, note that it's not unpacking a thrift object, it's unpacking the feature vector, which is filled with thrift objects. There may be a better way to do this but it's not related to the thrift api.

Copy link
Contributor

Choose a reason for hiding this comment

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

Well, I'm actually wondering if unpack-feature-vec is needed. Like, what about just mapping unpack over the sequence?

(map thrift/unpack seq)

Maybe?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It doesn't look like it would work to just map thrift/unpack right now. But you're right that this function could be made a lot cleaner (and renamed, probably).

Copy link
Contributor

Choose a reason for hiding this comment

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

Dan's right, there's a bit more than just using the thrift/unpacker going on here, and the feature vector has to be constructed exactly this way. It's definitely unwieldy though, so would be great to clean it up.

Create an issue?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah let's submit an issue for this.

@robinkraft
Copy link
Contributor

LGTM. #shipit

@danhammer
Copy link
Contributor Author

@eightysteele, if you think this looks good, maybe you could merge the pull request? Otherwise, let us know what is missing.

@eightysteele
Copy link
Contributor

@robinkraft, can you create an issue for unpack-feature-vec and then ship this mofo?

@danhammer
Copy link
Contributor Author

#shipit

On Fri, Jul 13, 2012 at 2:24 PM, Aaron Steele <
reply@reply.github.com

wrote:

@robinkraft, can you create an issue for unpack-feature-vec and then
ship this mofo?


Reply to this email directly or view it on GitHub:
#78 (comment)

robinkraft added a commit that referenced this pull request Jul 13, 2012
Incorporating thrift api into classify namespace
@robinkraft robinkraft merged commit e80c6dc into develop Jul 13, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants