Friday, September 9, 2016
inkscape latex math font
When a quick and simplistic latex-style formula is needed in Inkscape, the "Latin Modern Roman" font may be used. Latest versions of Inkscape incorporate buttons to create subscripts and supersripts when editing text.
Thursday, September 1, 2016
pyplot tex / latex interpreter
### setup use of TEX for labels ###
plt.rc('text', usetex=True)
plt.rc('font', family='serif')
### define label ###
s="\textbf{Bold}"
s= s.encode('string-escape')
ax.set_ylabel(s)
plt.rc('text', usetex=True)
plt.rc('font', family='serif')
### define label ###
s="\textbf{Bold}"
s= s.encode('string-escape')
ax.set_ylabel(s)
Monday, July 4, 2016
CUDA constant memory
http://stackoverflow.com/questions/22364926/cuda-invalid-device-symbol-error
http://stackoverflow.com/questions/19621380/cuda-how-to-access-constant-memory-in-device-kernel-when-the-constant-memory-is
http://stackoverflow.com/questions/19621380/cuda-how-to-access-constant-memory-in-device-kernel-when-the-constant-memory-is
Thursday, June 30, 2016
SVN list recently added files
example:
svn log -r{2016-06-06}:{2016-06-30} --verbose | grep ' A'
Src:http://stackoverflow.com/questions/27275375/how-to-retrieve-files-in-subversion-svn-recently-added-to-the-repository
svn log -r{2016-06-06}:{2016-06-30} --verbose | grep ' A'
Src:http://stackoverflow.com/questions/27275375/how-to-retrieve-files-in-subversion-svn-recently-added-to-the-repository
Monday, March 14, 2016
bibtex medphys missing book title
For now medphys.bst is bugged. If a book title is missing, remove the "year" field from .bib and append it to the "publisher" field
Tuesday, February 23, 2016
bash kill process by name
pkill -f csp_build.py
src: http://stackoverflow.com/questions/3510673/find-and-kill-a-process-in-one-line-using-bash-and-regex
Tuesday, January 26, 2016
How to use svn merge to preview svn update
How to use
svn merge to preview svn update- Change to the root directory of your working copy.
- Run the command:
Note: The trailing “dot” is the path of the working copy, and it is required even if you are already inside the working copy, which you should be after step 1.svn merge --dry-run -r BASE:HEAD .
- The above command requests a “dry run”
of what will happen if we receive all changes that occurred after our
working revision (BASE) and the most recent revision in the repository
(HEAD). This is what
svn updatedoes, too. - Review the output of
svn mergeand check for conflicts. If you spot any, try usingsvn diffto determine what is causing the conflict, or just prepare yourself to fix the conflict ASAP! - Now that you know how friendly or destructive
updatewill be with your working copy, runsvn updateto let the fun begin!
Subscribe to:
Posts (Atom)