Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob bob
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bob
  • bobbob
  • Issues
  • #121
Closed
Open
Created Apr 04, 2013 by André Anjos@andre.anjos💬Owner

Random initialization of arrays is inconsistent

Created by: laurentes

At the C++ level, there are several options to generate random numbers. Across the library, this is currently not consistent: We sometimes rely on blitz++ ranlib, sometimes on boost. In addition, few classes allow the user to set a boost random number generator, whereas others allow him to set a seed.

We have decided to follow this approach:

  • Always use boost at the C++ level
  • Classes that make use of random numbers should provide a way to set the boost random number generator. We still have to discuss whether it is better to handle the boost random number generator through a reference or a boost::shared_ptr.

The goal is aim to converge to this design. This will involve:

  • Make the JFATrainer use boost rather than ranlib
  • Remove the seed attribute from:
    • KMeansTrainer
    • PLDABaseTrainer (done by @laurentes)
  • Check if we keep using a reference (or a boost::shared_ptr) in the following classes
    • MLP
    • DataShuffler

Please be aware that this will slightly affect the results afterwards, as the initial random matrices will be different

Assignee
Assign to
Time tracking