-
Notifications
You must be signed in to change notification settings - Fork 0
Pull svmbatch development history into main MethodsCore repo #26
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
Merged
dankessler
merged 30 commits into
UMPsychMethodsCore:develop
from
dankessler:svmbatch/main
Mar 7, 2012
Merged
Pull svmbatch development history into main MethodsCore repo #26
dankessler
merged 30 commits into
UMPsychMethodsCore:develop
from
dankessler:svmbatch/main
Mar 7, 2012
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed file references to include '+orig'. Successful test run through on garbage data Updated readme file
1] If directory specified by svmdir doesn't exist, it will attempt to make it for you. 2] If you give the script an additional argument of 1, it will run a leave-one-out crossvalidation for you.
Added ability to do totem mode, significant rearrangement of argument/parameter processing, etc.
…nable settings for older, non-totem and linear applications.
…tionality is broken until it gets written back in. Hardcoded for crossval, which probably doesn't work anyway
…e small typo that had no present impact, but may if we use "test rules" in the future
… cases, rather than doing so with replacement after each LOOCV
… release to speed up processing
…atch work into the MethodsCore repo. It should not be viewed as the "final" svmbatch product
Member
Author
|
I'm going to assume this is ok with everybody and go ahead and merge it in. |
dankessler
added a commit
that referenced
this pull request
Mar 7, 2012
Pull svmbatch development history into main MethodsCore repo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was prompted by issue #18, which requested that the svmbatch history be integrated into the main methods core repository.
I did some git wizardry to make this cleaner, which I'll explain here and may help in the future.
My goal was for development of this to look like it had branched off of MethodsCore, rather than being developed independently. This required me to use some fancy filter-branch and rebase tricks.
Development Repository (svmbatch)
First, I went to the svmbatch repository where I had been developing all of this as the root tree.
Clean Up History
To clean up the history, which included some merges I didn't care about seeing as merges, I ran
git rebase
Filter-branch to put root in subtree
My goal was for it to look as if I had developed everything in a subtree called /svmbatch/
This went and, and for each commit reachable from HEAD (my current branch)
-pflag (among other things) suppresses errors when that subdirectory already existsin my local MethodsCore repo
I next needed to read in this history, and make it look like it had branched off of MethodsCore's develop branch
Reading in the data
When I run this I get a complaint about not common commits, which is totally to be expected since they their histories don't intersect. We'll fix this in a minute.
You can appreciate the nonintersection if you run
gitk --alland you'll see the two unconnected lineages.Basing things on develop
All Done!
Go ahead and run
gitk --alland you'll now see that it looks as if I grabbed MethodsCore, checked out develop as a new branch called svmbatch, then did all of my work in the subtree svmbatch (of course, the time stamps suggest otherwise).