Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gcForest
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Ji Feng
  • gcForest
  • Issues
  • #71
Closed
Open
Issue created Oct 02, 2019 by Dang Manh Truong@dangmanhtruong1995

gcForest for images

Hi. In the gcForest paper the author states that three sliding windows are used: d/16, d/8, d/4 are used, where d is the number of features. However I don't understand about the case for images. For example, with an image of size 472 * 677, for the case of d/16 would it be of size: (472 / 16) * (677 / 16), that would be a window size of (30, 43). The number of instances for one image would be: (472 - 30 + 1) * (677 - 43 + 1) = 281305. So the number of pixels would be: 281305 * 30 * 43 = 362883450. Compared to original: 472 * 677 = 319544 pixels. So the dataset would be bigger by 362883450 / 319544 = 1135.63 times. It seems to me that this would make the new dataset too big. I wonder if this is correct and what the author does to mitigate this? Thank you very much. Truong.

Assignee
Assign to
Time tracking