Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P PyFstat
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

ATTENTION: This Gitlab instance will undergo extended maintenance on 2023-04-12 at 06:00 UTC. The downtime will approximately take 1 hour. Please plan ahead accordingly. For questions please contact atlas_admin@aei.mpg.de

  • Gregory Ashton
  • PyFstat
  • Issues
  • #7
Closed
Open
Issue created Dec 12, 2017 by David Keitel@dkeitelMaintainer

add switches to override check_old_data_is_okay_to_use?

Both the grid and MCMC search classes have check_old_data_is_okay_to_use methods, which are a good idea in principle, but might need to get quite a bit more involved to check all possible differences between search calls in all use cases. (E.g. the simple grid output format currently cannot be used to distinguish between a search with and without t0,tau bands, which I'll open another issue about.)

So a nice convenience feature, at least for use during development, would be a 'reusedata' argument, default True, but when set to False just skips that check. If you like it, I can make a patch.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking