Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • P pycroscopy
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Vasudevan, Rama K
  • pycroscopy
  • Issues
  • #25

Closed
Open
Created Oct 25, 2016 by Vasudevan, Rama K@rvvMaintainer

Better index tracking in the model class

Created by: ssomnath

When reading a large dataset in chunks, the get_data method updates the start and end indices by itself. This would cause serious problems when fitting since the indices would have moved to the next chunk even before the get_guess method can be called. Need a better book-keeping method to keep track of indices of the current chunk

┆Issue is synchronized with this Asana task

Assignee
Assign to
Time tracking