grand_average.m pattern naming
GoogleCodeExporter opened this issue · 2 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. create a grand average pattern
2. create another grand average pattern with the same pattern but using
different event_bins
3. the events for the first ga_pattern will be overwritten by the events for
the second, etc.
What is the expected output? What do you see instead?
One would expect to have two different grand average patterns with their
corresponding events, but unless you specify different res_dir(s) the events
for the first pattern you created are overwritten by the second.
What version of the product are you using? On what operating system?
unsure, OSX
Please provide any additional information below.
A good fix might be to add the 'save_as' functionality from other functions
(e.g. bin_pattern.m) to the grand_average pattern...
Original issue reported on code.google.com by zachary....@gmail.com
on 14 Mar 2011 at 8:13
GoogleCodeExporter commented
I've changed the implementation to use bin_pattern. You should be able to use
all the usual save options now, including save_as.
Original comment by morto...@gmail.com
on 15 Mar 2011 at 3:41
- Changed state: Fixed
GoogleCodeExporter commented
turns out the issue was with the file name I had given it. If you have a space
at the beginning of your 'res_dir' , save doesn't work.
Fail: ' ~/results/'
Win: '~/results/'
Original comment by zachary....@gmail.com
on 28 Mar 2011 at 10:59