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

Problems creating GST pdf report #34

Closed
maximilianruf opened this issue Dec 4, 2017 · 1 comment
Closed

Problems creating GST pdf report #34

maximilianruf opened this issue Dec 4, 2017 · 1 comment

Comments

@maximilianruf
Copy link

When creating a brief pdf report using pygsti, using a default directory name with underscores creates a LaTex error. This is caused by a failing math interpretation of the directory name in the \hypersetup{pdfinfo={ \putfield{pdfinfo}{} }} section in the GST report template. Using \detokenize{directory_name} in the generated .tex file saves the problem, however this is not practical since this error is created every time when creating a new report. For now, my workaround is to pop the key 'defaultDirectory' before calling the function _to_pdfinfo in pygsti's results.py. When using several computers, this becomes cumbersome.

@enielse
Copy link
Collaborator

enielse commented Mar 9, 2018

Thanks for pointing this out. I believe this may be a Windows-only issue(?). In any case, the recently released pyGSTi v 0.9.4 addresses this issue in two ways:

  1. Reports are now by default in HTML format rather than PDF, so there's no pdfinfo metadata to be an issue. Note that the report-generation function in v0.9.4 is pygsti.report.create_standard_report(...) and that report generation has changed slightly so you may want to checkout the report generation tutorial.
  2. If you still want a PDF report, you can just give a ".pdf" output name to create_standard_report. In this case, we've now removed a bunch of the unnecessary metadata from the PDF including the "default directory", so you shouldn't have any LaTeX problems compiling it.

I'll mark this thread as closed since the original issue has definitely been removed. If you have any other problems with report generation please create a new issue or reopen this one as you see fit.

@enielse enielse closed this as completed Mar 9, 2018
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

No branches or pull requests

2 participants