Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to Refactor SimultaneousFitPage Class (Trac #942) #1021

Open
butlerpd opened this issue Mar 30, 2019 · 2 comments
Open

Need to Refactor SimultaneousFitPage Class (Trac #942) #1021

butlerpd opened this issue Mar 30, 2019 · 2 comments
Labels
Defect Bug or undesirable behaviour Enhancement Feature requests and/or general improvements Minor Small job
Milestone

Comments

@butlerpd
Copy link
Member

butlerpd commented Mar 30, 2019

It turns out that the !SimultaneousFitPage class in simfitpage.py is used both for constrained/simultaneous fitting and for combined batch fitting. Most of th page is the same but there are a dozen instances requiring one or two lined of code change that are all done using "if batch_on...."

This is bad form. Ideally the class should be rewritten to be generic and then two subclasses written which inherit from that class. All could reside in the one file.

However, since this is in sasgui which goes away soon and does not affect the user experience it has a trivial priority and will presumably be closed as obsolete after 5.0 if not fixed first.

Migrated from http://trac.sasview.org/ticket/942

{
    "status": "new",
    "changetime": "2017-10-23T14:28:03",
    "_ts": "2017-10-23 14:28:03.845491+00:00",
    "description": "It turns out that the !SimultaneousFitPage class in simfitpage.py is used both for constrained/simultaneous fitting and for combined batch fitting.  Most of th page is the same but there are a dozen instances requiring one or two lined of code change that are all done using \"if batch_on....\"\n\nThis is bad form.  Ideally the class should be rewritten to be generic and then two subclasses written which inherit from that class.  All could reside in the one file.\n\nHowever, since this is in sasgui which goes away soon and does not affect the user experience it has a trivial priority and will presumably be closed as obsolete after 5.0 if not fixed first.",
    "reporter": "butler",
    "cc": "",
    "resolution": "",
    "workpackage": "SasView Framework Enhancements",
    "time": "2017-04-09T14:28:50",
    "component": "SasView",
    "summary": "Need to Refactor SimultaneousFitPage Class",
    "priority": "trivial",
    "keywords": "",
    "milestone": "SasView 5.0.0",
    "owner": "",
    "type": "defect"
}
@butlerpd butlerpd added this to the SasView 5.0.0 milestone Mar 30, 2019
@butlerpd butlerpd added Defect Bug or undesirable behaviour Incomplete Migration and removed Incomplete Migration labels Mar 30, 2019
@butlerpd
Copy link
Member Author

Trac update at 2017/10/23 14:28:03:

  • butler commented:

No point in doing this in old gui. Probably irrelevant in new GUI but move to 5.0 for now anyway?

  • butler changed milestone from "SasView 4.2.0" to "SasView 5.0.0"

@rozyczko
Copy link
Member

I'd like to keep this since I want to refactor FittingWidget for 5.1
This module grew enormously and is due for serious refactoring.

@rozyczko rozyczko modified the milestones: SasView 5.0.0, SasView 5.1.0 May 15, 2019
@lucas-wilkins lucas-wilkins added Minor Small job and removed trivial labels Jul 19, 2022
@lucas-wilkins lucas-wilkins added Enhancement Feature requests and/or general improvements and removed Migrated from Trac labels Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defect Bug or undesirable behaviour Enhancement Feature requests and/or general improvements Minor Small job
Projects
None yet
Development

No branches or pull requests

3 participants