{5} Accepted, Active Tickets by Owner (Full Description) (10 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

ajj (3 matches)

Ticket Summary Component Milestone Type Created
Description
#845 Fix volume normalisation on Raspberry model sasmodels SasView 4.3.0 defect Feb 7, 2017

As noted in #815 the raspberry model needs to be doing volume calculation outside Iq function to get polydispersity working properly.


#303 Integrate user and developer websites SasView Admin Tasks enhancement Feb 12, 2015

To minimise the proliferation of resources we are using we should try to merge the website and trac etc to be integrated and hosted together.


#23 Provide ability to submit bug report directly from SasView SasView SasView Next Release +1 enhancement Mar 29, 2012

There should be a means of submitting bug reports directly from SasView. These should probably go directly into Trac with some tag to allow someone to sort and classify them


butler (1 match)

Ticket Summary Component Milestone Type Created
Description
#299 write SasView Paper SasView Admin Tasks task Feb 1, 2015

There are several papers that could be written about specifc implentations but need a general paper that can be used as a reference. As long as the online documentation is in good shape can point to that as "suppl material"?


piotr (1 match)

Ticket Summary Component Milestone Type Created
Description
#246 Fix problem with with dire install warnings from OS SasView Admin Tasks task Apr 19, 2014

Currently on newer Windows machines and some macs the operating system gives several dire warnings against installing the executable SasView? appliation. In fact in some cases the default is to not allow install and only by right clicking can one get options to "install anyway".

Somehow this needs to be fixed. Should look at what mac and windows will require - do we need to get a certification? how?


richardh (1 match)

Ticket Summary Component Milestone Type Created
Description
#1020 orientation - write a chapter for the general users docs sasmodels SasView 4.3.0 enhancement Oct 27, 2017

orientation - write a chapter for the general users docs, that can be referenced from individual models. See also ticket #776


tim (4 matches)

Ticket Summary Component Milestone Type Created
Description
#594 Check default value of cansas_version property in CansasReader class SasView SasView 4.3.0 task Jul 22, 2016

(Ticket raised on behalf of Lewis) CansasReader has a property cansas_version which determines the xml header written in the files. This currently seems to default to 1.0 and not 1.1 as you get the old header if you call this class directly. However if you save xml files from the GUI they are saved with the new header! This suggests the default is over-ridden somewhere. Needs investigating.


#812 Provide model for the Pringle-Schmidt helical form factor sasmodels SasView 4.3.0 enhancement Nov 24, 2016

Request from Ian Hamley (i.w.hamley@…):

Would be possible to incorporate the Pringle-Schmidt helical form factor into SasView? It is used in quite a few studies now. There are other helical form factors (see attached) but the Pringle-Schmidt form factor is more generally and more widely used.

I don’t have code although I know some people who might – Heinz Amenitsch or Pierre Terech. These two groups also have data and fits in their papers.

I have datasets waiting to be fitted, as does Daniel Hermida-Merino at the ESRF.


#565 Update check_packages to flag required package versions SasView Admin Tasks enhancement Apr 26, 2016

check_packages could be made to flag when the installed packages (eg, bumps) do not meet the minimum version number necessary for a successful build.


#806 clean separation between sasmodels and sasview SasView SasView 4.3.0 enhancement Nov 14, 2016

sasmodels should act like an indpendent third party package without knowledge of sasview internals. This is not the case in a few places:

  • sasview_model.py belongs in sasview. It was developed within sasmodels for convenience, but now that sasmodels is mature it can be moved to sasview.
  • sasmodels should not have knowledge of the sasview data representation. Currently this infects resolution.py, resolution2d.py and sesans.py. data.py was set up as a clone of the sasview data structures for testing, and this has infected direct_model.py, bumps_model.py and compare.py. Perhaps we could create a sasdata package which both sasview and sasmodels depend upon, or perhaps the data representation could move (along with the loaders?) to sasmodels.
  • compare.py imports models from sasview 3.x for test purposes; this code will eventually disappear once we are certain we no longer need to compare against 3.x
  • convert.py includes knowledge of the 3.x model parameters and how they relate to the new sasmodels parameters. This information should stay in sasmodels, along with any future model migration code.
  • sasmodels documentation currently living in sasview/src/sasgui/perspectives/fitting/media/plugin.rst mostly belongs in sasmodels docs.

Note: See TracReports for help on using and creating reports.