| T O P I C R E V I E W |
| jdf726 |
Posted - 02/19/2019 : 2:16:46 PM
Origin Ver. and Service Release (Select Help-->About Origin): 2018 Pro
Operating System: Win 7
It is the intended behaviour to have the error bars missing when using clip data to frame with negative margins? (10% here)
J.
PS: I also don't know how I ended up with a dot dash line format on my error bar lines...
I plotted the Y errors using the plotxy with three arguments for iy:=(x,y,dy) then did this for the x errors.
layer -i202 rdX;
set rdX -ox rY;
range rr = !1; set rr -c 2; //data points type
range rr = !2; set rr -z 2;//cap widths on error bars
range rr = !3; set rr -z 2;
range rr = !2; set rr -w 1;//line widths on error bars
range rr = !3; set rr -w 1; |
| 7 L A T E S T R E P L I E S (Newest First) |
| alice009 |
Posted - 03/02/2019 : 04:02:09 AM
I am also faced oxe5 epson error problem many times. I am trying too many times to solve this problem but I can't do that that's why I want a solution on this problem as soon as possible.i have also checked https://www.epsonsupport247.com/epson-printer-error-code-0xe5-solved/ for a solution. |
| Castiel |
Posted - 02/21/2019 : 05:30:02 AM
quote:
Originally posted by jdf726
I am not plotting into a particular template, just doing win -t plot; (I think this uses the default 'Origin' template, right?).
The default "origin" template can be changed. For example, hide the X axis and Save Template (As...) as Origin, then "win -t plot" would create a graph without X axis.
I'm not familiar with LabTalk and did not try your code yet. I prefer OriginC to LabTalk in that the former one is easier to understand.
&&&&&&&&&
&&&
&&
& _____ ___________
II__|[] | | I I |
| |_|_ I I _|
< OO----OOO OO---OO
**********************************************************
|
| jdf726 |
Posted - 02/21/2019 : 04:40:04 AM
Hi Castiel and Shirley, thanks for your help.
I wouldn't normally use plot designations unless I have to (is that a Labtalk crime?)
I also don't normally highlight columns to plot but use plot setup dialog (manually) or range notation (in code). Maybe this is where I am going wrong.
Designations seem to allow the graphing routine to pick 'iy:=' type arguments up 'implicitly', but I don't know what happens when the plot designations are conflicting or are changed during the script; I often have multiple output plots per dataset, sometimes a column is the 'X' of one plot but the 'Y' of another plot!
Castiel mentions the template. I am not plotting into a particular template, just doing win -t plot; (I think this uses the default 'Origin' template, right?).
I have pasted in some of the code below so you can see what I am doing. Note that if I do not set the line/cap width in my plot to some finite number it is zero in the GUI and the bars are invisible.
I have tried to understand Castiel's comment about the style being locked, and I see that the line style gets locked when you check the X-error bar option.
During this I discovered that if I comment out the set -ox command, adding error bars with just the layer -i233 command (and designations) works!
In fact, without column designations, 'set .. -ox ..' doesn't seem to do anything, and just gives me weird 'dot dash' lines on the x-error bars when it is applied IN ADDITION to 'layer -i233' with designations.
J.
opb$='';
doc -ef LB {if (search(page.longname$,"P02")>0) {opb$ = page.name$;}} //Loop over books and find certain fragment
win -t plot; //Make a new plot window
G$ = page.name$; //get it's name
G$=;
win -r %(G$) "%(opb$)p0p2"; //Rename the book
label -px 5 5 -s -sl -n ttext %Z; //Insert label into plot
ttext.fsize = 14; //Set font size
range wkb = [opb$]1!; //
range rX = [opb$]1!Col("V"); //Ranges for data...
range rP0 = [opb$]1!Col("P0"); //
range rP1 = [opb$]1!Col("P1"); //
range rP2 = [opb$]1!Col("P2"); //
range rdP0 = [opb$]1!Col("dP0"); //and error bars
range rdP1 = [opb$]1!Col("dP1"); //
range rdP2 = [opb$]1!Col("dP2"); //
plotxy iy:=(rP0,rP2,rdP2) plot:=201 ogl:=["%(opb$)p0p2"]1!; //insert plot with Y error bars
wkb.col = 9; //Set active column to set designations
wkb.col.type = 4; //Set P0 as an X
wkb.col = 12; //Set error bars
wkb.col.type = 7; //Set x-error designation
layer -i233 rdP0; //Add error bars plot
set rdP0 -ox rP2; //Associate errors with Y data
range rr = !1; set rr -z 4; //data points
range rr = !1; set rr -k 2; //data points
range rr = !1; set rr -c 2; //data points type
layer -b c 0; //turn off clip data to frame
range rr = !2; set rr -z 2; //cap widths on error bars
range rr = !3; set rr -z 2;
range rr = !2; set rr -w 500; //line widths on error bars
range rr = !3; set rr -w 500; //line widths on error bars
layer 60 60 20 30; //Dimension the plot layer in % units
layer.x.from = 0; //axis limits
layer.x.to = 0.5;
layer.x.inc = 0.25;
layer.y.from = 0;
layer.y.to = 0.5;
layer.y.inc = 0.25;
layer.x.minorticks = 4;
layer.y.minorticks = 4;
layer.x.showGrids=3;
layer.y.showGrids=3;
layer.x.grid.majorColor = 0;
layer.y.grid.majorColor = 0;
layer.x.grid.majorColor = 0;
layer.y.grid.majorColor = 0;
layer.x.grid.majorType = 1;
layer.y.grid.majorType = 1;
layer.x.grid.majorWidth = 1;
layer.y.grid.majorWidth = 1;
layer.x.grid.minorColor = 0;
layer.y.grid.minorColor = 0;
layer.x.grid.minorType = 3;
layer.y.grid.minorType = 3;
layer.x.grid.minorWidth =1;
layer.y.grid.minorWidth =1;
themeApply2g theme:=ClippingMargins;
expGraph type:=png filename:="<long name>" path:="<Project Folder>\\png\\" theme:=<Original> tr.Margin:=2 overwrite:=replace; |
| Shirley_GZ |
Posted - 02/21/2019 : 02:16:14 AM
Hi Jim,
The X-Function "plotxy" doesn't support four arguments, to plot XYXErrorYError at same time into a graph, you can first set col(1)~col(4) as X/Y/XErr/YErr, and then
Method 1:
Use plotxy to plot a XYYErr plot and then use layer -i233 to add the X Error, such as
plotxy plot:=201 iy:=(1,2,4);
layer -i233 Book1_C;
Method 2:
Run LabTalk script lines:
worksheet -s 0 0 0 0; //Highlight 4 columns
worksheet -p 201 Scatter; //Plot the columns as scatter with X and Y error bars
Thanks,
Shirley
Originlab Technical Service Team |
| Castiel |
Posted - 02/20/2019 : 9:58:51 PM
quote:
Originally posted by jdf726
Thanks!
Perhaps you can explain to me something about how to add error bars. Perhaps I have done something wrong because there is something buggy going on - the rendered line style (dot dash) for the error bars is not consistent with what the GUI reports (solid) when I click on the data set. If I assert solid with the GUI, it works.
The ingredients to the plot are (obviously)
* X data
* Y data
* X error data
* Y error data
but I started to realise that there was a list of 'things that might or might not be important'
1) There are (at least) two ways of adding data to a graph, either using plotxy or layer -iXXX, does it matter re. error bars?
2) Do you HAVE to use the correct i-code (233?) to add error bars?
3) Do column designations have to be set?
4) Do I have to plot the error bar data before I call set...-ox... ?
5) Can I use themeapply2g to overwrite the weird dot dash lines?
You would think I could answer these by now, but I still have dot-dash lines on my error bars for no apparent reason and the programmatical line width units are weird (setting line width of '500' in labtalk is equivalent to one pt in the GUI).
The answers would appear to be
1) No (but the formatting is still odd).
2) No (but with odd formatting)
3) I don't think so, but I added this anyway
4) Yes. https://www.originlab.com/doc/LabTalk/ref/Options_for_Error_Bars#-ox, but does what I plot the error bars as initially (line/scatter) have any impact on the formatting when they are adopted as error bars?
5) Maybe...fixes line width but tends to make the Y error bars magically become designated as X error bars or vice versa when I tried it!
Basically, I'd like a version of plotxy with four arguments for iy:= to include x errors and some labtalk to set the error bar properties robustly.
About the "weird dot dash lines". Did you change the ErrBar template? Is it dot dash lines in the graph created manually? The designations should be ordered as X, Y, Y Error, X Error (Yes, the last one is X Error).
In Plot Details - Plot Properties, when direction is not X Error Bar, and the Connect is not No Line, you can change the Style to solid, dash, etc. Once applied, changing the Connect = No Line and Direction = X Error Bar would not change the Style (in your case weired dot dash line). You can save the template/theme once the styles corrected.
Ctrl+Shift+Click X Y Error bar will show you the LabTalk script creating XYError graph. It's set...-ox... that changes the plotted one to X Error.
&&&&&&&&&
&&&
&&
& _____ ___________
II__|[] | | I I |
| |_|_ I I _|
< OO----OOO OO---OO
**********************************************************
|
| jdf726 |
Posted - 02/20/2019 : 1:09:02 PM
Thanks!
Perhaps you can explain to me something about how to add error bars. Perhaps I have done something wrong because there is something buggy going on - the rendered line style (dot dash) for the error bars is not consistent with what the GUI reports (solid) when I click on the data set. If I assert solid with the GUI, it works.
The ingredients to the plot are (obviously)
* X data
* Y data
* X error data
* Y error data
but I started to realise that there was a list of 'things that might or might not be important'
1) There are (at least) two ways of adding data to a graph, either using plotxy or layer -iXXX, does it matter re. error bars?
2) Do you HAVE to use the correct i-code (233?) to add error bars?
3) Do column designations have to be set?
4) Do I have to plot the error bar data before I call set...-ox... ?
5) Can I use themeapply2g to overwrite the weird dot dash lines?
You would think I could answer these by now, but I still have dot-dash lines on my error bars for no apparent reason and the programmatical line width units are weird (setting line width of '500' in labtalk is equivalent to one pt in the GUI).
The answers would appear to be
1) No (but the formatting is still odd).
2) No (but with odd formatting)
3) I don't think so, but I added this anyway
4) Yes. https://www.originlab.com/doc/LabTalk/ref/Options_for_Error_Bars#-ox, but does what I plot the error bars as initially (line/scatter) have any impact on the formatting when they are adopted as error bars?
5) Maybe...fixes line width but tends to make the Y error bars magically become designated as X error bars or vice versa when I tried it!
Basically, I'd like a version of plotxy with four arguments for iy:= to include x errors and some labtalk to set the error bar properties robustly.
|
| Shirley_GZ |
Posted - 02/20/2019 : 03:30:50 AM
Hi jim,
For the disappeared error bar, this could be a bug, I have submitted a jira to follow up this issue, ORG-19729.
To set the connect line style of the X/Y error bar, I am afraid we don't have any more LabTalk and GUI control to change the connect line style to dot dash for the error bars.
Please let me know if you have any problem!
Thanks,
Shirley
OriginLab
Originlab Technical Service Team |
|
|
