[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53070] Empty search path when starting Octave
From: |
Peter Langer |
Subject: |
[Octave-bug-tracker] [bug #53070] Empty search path when starting Octave from TCC/LE (alternative Windows command prompt) |
Date: |
Fri, 9 Feb 2018 02:29:13 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko |
Follow-up Comment #8, bug #53070 (project octave):
The renaming of the bug is OK!
Trying octave.vbs instead of octave-gui.exe in TCC-LE (because octave.bat is
not working):
1. On the local computer(Win7): it’s just works fine (e.g.
D:\Programme\Octave-4.2.1\Octave.vbs test.m)
2. On the local computer this works too:
\\R176\BKG_Programme$\Octave\Octave_4.2.1\Octave.vbs test.m
3. using a remote session on one computer in the cluster (Windows 2012
Server
R2) this works too: C:\BKG_Programme\Octave\Octave_4.2.1\Octave.vbs test.m
4. using a remote session on one computer in the cluster (Windows 2012
Server
R2) the following makes errors (ghostscript related):
\\R176\BKG_Programme$\Octave\Octave_4.2.1\Octave.vbs test.m
warning: called from
__print_parse_opts__>__ghostscript_binary__ at line 506 column 26
__print_parse_opts__ at line 190 column 31
print at line 315 column 8
test.m at line 159 column 1
warning: print.m: Ghostscript binary is not available.
Only eps output is available.
warning: called from
__print_parse_opts__ at line 382 column 7
print at line 315 column 8
test.m at line 159 column 1
error: __ghostscript__.m: ghostscript is required.
error: execution exception in test.m
5. If I put the input from 3. in a job and arrange it that way, that the
job
is running at the same computer in the cluster like used for the test in 3.
the job does not run. If I replace Ocatve.vbs again and use octave-gui.exe
instead the job runs in the cluster.
The mentioned printing issue:
- Yes, I’m using a remote headless computer.
- Yes, I already tried different graphics_toolkits. Ordninary “qt” is
used. The warnings I already posted in comment #6 are a result from using
“qt”. I used the following command:
print('figure3.png','-dpng', ['-S' num2str(1200) ',' num2str(768)]);
The funny thing is: It’s working fine, if I use:
print('figure3.png','-dpng', ['-S' num2str(1000) ',' num2str(667)]);
- The toolkit “fltk” it not working right.
- With “gnuplot” the size of the graphic is OK. The whole graph but looks
ugly because the linewidth is the same all over the graph.
Whit all those problems I'm fighting right now I’m getting the feeling not
to be right with octave. Maybe I should get python with matplotlib a chance.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53070>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #53070] running batch script from local hard drive via running it from a share (unc-path), Peter Langer, 2018/02/05
- [Octave-bug-tracker] [bug #53070] running batch script from local hard drive via running it from a share (unc-path), Markus Mützel, 2018/02/05
- [Octave-bug-tracker] [bug #53070] running batch script from local hard drive via running it from a share (unc-path), Peter Langer, 2018/02/06
- [Octave-bug-tracker] [bug #53070] Empty search path when running Octave from a network share (UNC path), Markus Mützel, 2018/02/06
- [Octave-bug-tracker] [bug #53070] Empty search path when running Octave from a network share (UNC path), Peter Langer, 2018/02/06
- [Octave-bug-tracker] [bug #53070] Empty search path when running Octave from a network share (UNC path), Markus Mützel, 2018/02/06
- [Octave-bug-tracker] [bug #53070] Empty search path when running Octave from a network share (UNC path), Peter Langer, 2018/02/07
- [Octave-bug-tracker] [bug #53070] Empty search path when starting Octave from TCC/LE (alternative Windows command prompt), Markus Mützel, 2018/02/07
- [Octave-bug-tracker] [bug #53070] Empty search path when starting Octave from TCC/LE (alternative Windows command prompt),
Peter Langer <=