Changes between Version 21 and Version 22 of DevNotes/Obsolete/v3p1PunchList
- Timestamp:
- Jun 30, 2015 11:13:37 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevNotes/Obsolete/v3p1PunchList
v21 v22 13 13 14 14 3. I think, from experiment with data rather than looking at the code, the docs for the Hayter MSA structure factor needs to note that even if no salt has been specifically added to the sample, the “salt conc” may need to be non-zero to allow for counterions that have come off say a micelle as it charges up. One day I will code up a version of the Hayter MSA where the Debye length is explicitly entered. NOTE added by PDB: I'm not sure that is true. The implication fromt the documentation (again without delving deeply into the code) is that the counterions are accounted for (assumed to be monovalent one per charge on colloid). The documentation already indicates that currently the ionic strength cannot be directly entered and that the counterions and salts are all assumed mono-valent. 15 >''' CHECK'''15 >'''TICKET FOR NEXT RELEASE''' 16 16 17 17 4. The “help about” box does not report the exact build number, just has 1> … … 19 19 20 20 5. Why are the parameter errors now appearing in red? (Which we usually keep around here for “fault” messages, so is giving me unnecessary stress.) - NOTE added by PDB: Vaguely remember adding red when something was wrong. Also limits sometimes show up prepopulated. QUESTION: are we accidentally using the new sasmodels? ANSWER: No. 21 >''' CHECK'''21 >'''TO FIX - MIGUEL''' 22 22 23 23 6. If I set up 3 data sets with constraints, say have M2.radius=M1.radius, M3.radius=M1.radius but then fix M1.radius at say 30 ang, I would expect the constraints to still work, but I get error message on hitting Fit in constraints page. … … 49 49 50 50 If anyone wants a simple 3 contrast core/shell microemulsion project, with real SANS data, to test the above just ask. I am grateful that “Save project” does now actually save all 3 data sets and models. (It would be nice if it also remembered which parameters are on/off, and in the +1 release, saved the constraints also, so that a fully working project could be emailed to someone else, as setting up the constraints etc is still non-trivial.) 51 >''' CHECK'''51 >'''NEXT RELEASE IF NOT FOUND''' 52 52 53 53 7. In Model Documentation, the Table of contents on left side has repeats of sections 2.2, 2.3 and 2.4. (There is also a note at top of screen about proof reading, which is no doubt still true!) … … 72 72 a. Docs are not included in python egg 73 73 b. Reports can not be generated 74 >''' CHECK'''74 >'''ADD TO TICKET''' 75 75 76 76 14. On mac when loading project, the following is repeated multiple times: … … 89 89 ERROR: In Order To Append/Insert A MultiLine Text You Have To Use The Style TR_HAS_VARIABLE_ROW_HEIGHT 90 90 }}} 91 >'''CHECK - NEXT RELEASE IF NOT OBVIOUS''' unless doesn't work for mac or gives error on mac
