June 2010 - Nexpy-dev - mailman3.cels.anl.gov

[nexpy] #19: Plot window signal tab
by nexpy 13 Sep '10

13 Sep '10

#19: Plot window signal tab ----------------------------+----------------------------------------------- Reporter: John Castellan | Owner: nobody Type: bug | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | ----------------------------+----------------------------------------------- The limits for the signal tab are fixed to some predetermined values. If you try to change them to arbitrary values outside the initial ranges it won't accept them. For instance starting a plot will give a range say 0 to 10 for the signal bar. Say I want to change the maximum to something larger than 10. It won't accept that, it will just reset to 10. The same is true for the min. -- Ticket URL: <http://trac.mcs.anl.gov/projects/nexpy/ticket/19> nexpy <http://trac.mcs.anl.gov/projects/nexpy> My example project

1 1

Re: [Nexpy-dev] NeXpy release
by Jason Sarich 29 Jun '10

29 Jun '10

Ray, I've reverted the repository back to where revision 210 was and will keep my development local until something stable is achieved. We'll have to discuss branch strategies when you get back. Jason On Tue, Jun 29, 2010 at 6:28 AM, Ray Osborn <ROsborn(a)anl.gov> wrote: > Jason, > I will be giving my presentation to the conference later today, but clearly > the current version with the new functionality is not ready for release. > Would it be possible to revert to a semi-stable earlier version, without the > extra plot windows on the public server, and then we can try and sort out > the remaining issues with private copies until the functionality is more > complete? Obviously, we need to have some kind of way of packaging versions, > which we can discuss when I get back. > > I don't know if my Mercurial history will match yours, but I am wondering > about reverting to revision 210, which was the last version before you > started using wxmpl, i.e., the version before June 21. > > What I hope to do is warn people that they would be downloading an > unfinished product, request that they specifically report any bugs on the > Trac server, but at least know that what they download has roughly the > functionality contained in the documentation. > > Thanks, > Ray > -- > Ray Osborn > Materials Science Division > Argonne National Laboratory > Argonne, IL 60439, USA > Phone: +1 (630) 252-9011 > Email: ROsborn(a)anl.gov > > > >

1 0

new dependency - wxmpl
by Jason Sarich 21 Jun '10

21 Jun '10

I have added the option of selecting axes for nexpy to plot. It is still preliminary -- no checks yet to make sure that x-axis and y-axis are uniquely selected and it hasn't been tested much yet. The zoom and/or change summation options is almost working, but I am adding a new library to the requirements list, wxmpl (at http://agni.phys.iit.edu/~kmcivor/wxmpl/<http://agni.phys.iit.edu/%7Ekmcivor/wxmpl/%29>). It is very straightforward to install (python setup.py install), at least on linux. Let me know if there are any problems on the mac. Jason

1 0

[nexpy] #13: Plotting projections through right-click
by nexpy 15 Jun '10

15 Jun '10

#13: Plotting projections through right-click -------------------------------+-------------------------------------------- Reporter: rosborn | Owner: nobody Type: new functionality | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | -------------------------------+-------------------------------------------- Allow slices of data to be created by dragging rectangles, with a right- click to set options. These should include 1) zoom of 2D plot to rectangle 2) one- or two-D plots of projections of the data along x0, x1, x2, ... Slice syntax --------- * 2D data->1D vs x0 - data[x0min:x0max,x1min:x1max].nxsum(1) * 2D data->1D vs x1 - data[x0min:x0max,x1min:x1max].nxsum(0) * 3D data->2D vs x0,x1 - data[x0min:x0max,x1min:x1max,x2min:x2max].nxsum(2) * 3D data->2D vs x0,x2 - data[x0min:x0max,x1min:x1max,x2min:x2max].nxsum(1) * 3D data->2D vs x1,x2 - data[x0min:x0max,x1min:x1max,x2min:x2max].nxsum(0) * 3D data->1D vs x0 - (data[x0min:x0max,x1min:x1max,x2min:x2max].nxsum(1)).nxsum(1) * 3D data->1D vs x1 - (data[x0min:x0max,x1min:x1max,x2min:x2max].nxsum(0)).nxsum(1) * 3D data->1D vs x2 - (data[x0min:x0max,x1min:x1max,x2min:x2max].nxsum(0)).nxsum(0) -- Ticket URL: <https://trac.mcs.anl.gov/projects/nexpy/ticket/13> nexpy <https://trac.mcs.anl.gov/projects/nexpy> My example project

1 1

[nexpy] #12: Rounded axis limits
by nexpy 08 Jun '10

08 Jun '10

#12: Rounded axis limits -------------------------+-------------------------------------------------- Reporter: rosborn | Owner: nobody Type: enhancement | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | -------------------------+-------------------------------------------------- There is padding around every NeXpy plot, presumably caused by rounding the axis limits up. This causes problems, particularly with signal limits on one-dimensional plots. Signal limits are implemented by clipping excess values, but this produces a flat top or bottom clearly visible on the plot. If someone sets axis limits, I think they would expect that plots would exactly cover those limits. -- Ticket URL: <https://trac.mcs.anl.gov/projects/nexpy/ticket/12> nexpy <https://trac.mcs.anl.gov/projects/nexpy> My example project

1 1

[nexpy] #17: Tree renaming bug
by nexpy 08 Jun '10

08 Jun '10

#17: Tree renaming bug ---------------------+------------------------------------------------------ Reporter: rosborn | Owner: nobody Type: bug | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | ---------------------+------------------------------------------------------ After renaming an item on the GUI tree, it is not available under the new name in the shell. -- Ticket URL: <https://trac.mcs.anl.gov/projects/nexpy/ticket/17> nexpy <https://trac.mcs.anl.gov/projects/nexpy> My example project

1 2

[nexpy] #11: Duplicate entries on the tree
by nexpy 08 Jun '10

08 Jun '10

#11: Duplicate entries on the tree ---------------------+------------------------------------------------------ Reporter: rosborn | Owner: nobody Type: bug | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | ---------------------+------------------------------------------------------ If a second assignment is made to a node already on the GUI tree, instead of overwriting the node, a second node of the same name is created. -- Ticket URL: <https://trac.mcs.anl.gov/projects/nexpy/ticket/11> nexpy <https://trac.mcs.anl.gov/projects/nexpy> My example project

1 1

[nexpy] #18: Window resizing
by nexpy 08 Jun '10

08 Jun '10

#18: Window resizing ---------------------+------------------------------------------------------ Reporter: rosborn | Owner: nobody Type: bug | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | ---------------------+------------------------------------------------------ At the moment, if I resize the NeXpy window by dragging the bottom boundary, I only resize the axis limits toolbar. This means I can only resize the scripting window by dragging the bottom boundary and then dragging back the axis limit bottom boundary. The axis limit toolbar should be a fixed height with only width adjustments possible. -- Ticket URL: <https://trac.mcs.anl.gov/projects/nexpy/ticket/18> nexpy <https://trac.mcs.anl.gov/projects/nexpy> My example project

1 2

[nexpy] #10: Need to add colorbar
by nexpy 02 Jun '10

02 Jun '10

#10: Need to add colorbar -------------------------+-------------------------------------------------- Reporter: rosborn | Owner: nobody Type: enhancement | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | -------------------------+-------------------------------------------------- Two-dimensional plots should have a color bar to the right of the main plot. -- Ticket URL: <https://trac.mcs.anl.gov/projects/nexpy/ticket/10> nexpy <https://trac.mcs.anl.gov/projects/nexpy> My example project

1 1

[nexpy] #9: Line editing behavior in the Pyshell
by nexpy 02 Jun '10

02 Jun '10

#9: Line editing behavior in the Pyshell -------------------------+-------------------------------------------------- Reporter: rosborn | Owner: nobody Type: enhancement | Status: new Priority: major | Milestone: Component: GUI | Version: Keywords: | -------------------------+-------------------------------------------------- Is it possible to swap the behavior of the 'cursor arrow' and 'shift- cursor arrow' in the pyshell? i.e., pressing the up-arrow will give the previous command (not shift-up-arrow). Ideally, I would like the behavior to mimic that in iPython. -- Ticket URL: <https://trac.mcs.anl.gov/projects/nexpy/ticket/9> nexpy <https://trac.mcs.anl.gov/projects/nexpy> My example project

1 1