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

fig naming and report compiling #3

Open
GoogleCodeExporter opened this issue Jun 9, 2015 · 2 comments
Open

fig naming and report compiling #3

GoogleCodeExporter opened this issue Jun 9, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.run pat_topoplot.m to plot topoplot figures
2. run pat_report.m , specifying the time (3rd) dimension
3. if time bins are ranges, not averages, labels will cause an error

What do you see?

compiling ~/results/reports/vf_2000_glm_rb_abs60_Zd_k4_topo_ic_report...
dvips: Could not find figure file \protect \unhbox \voidb@x \penalty \@M \ 
{}/results/reports/figs/vf_2000_glm_rb_abs60_Zd_k4_topo_ic_ga_0-to-250-ms.eps; 
continuing

Please provide any additional information below.
I'm not sure, but looking back at previous calls to this function, topoplots 
from different time bins were name using the format, "_e#t#f#.eps" , where the 
#s corresponded to the event#, time#, and frequency#. now, it seems that the 
topoplot is being named using the time bin label, which includes dashes. it 
would seem this might be leading to the error.

Original issue reported on code.google.com by zachary....@gmail.com on 14 Mar 2011 at 8:54

@GoogleCodeExporter
Copy link
Author

and by event#, I meant electrode#... (a.k.a. channel#). 

Original comment by zachary....@gmail.com on 14 Mar 2011 at 8:56

@GoogleCodeExporter
Copy link
Author

I don't know of problems with dashes in LaTeX, but if that's the problem it's 
simple to fix.  I've attached a version of pat_topoplot that should produce 
files with underscores instead of dashes.  Let me know if this works.

I also wonder if the ~ in your filepath might cause an issue; some programs 
don't know how to translate a ~ to your home directory.  So you could also try 
using an absolute path e.g. /home/mortonne/...

Original comment by morto...@gmail.com on 9 Jun 2011 at 5:49

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant