Clean object classifications in documentation rendered theme about carrot

[christianechevarria]

@christianechevarria I find it easier - conceptually - to imagine architect.[architecture] - as just an extension of Network.

Would you be cool with - or do you think it's easier to understand - creating networks with different architectures as Network.architecture.[architecture]?

For Example

let new = new Network.architecture.LSTM(365, 12) // Creates an LSTM with 365 input neurons and 12 output neurons.

As an additional note:

• We can leave the architect/architecture namespaces and classes for classes and functions that actually help create the network structure/topologies (i.e. NEAT or Instinct Algorithms). I find these to personally fit the term "architect" better since they are network designing algorithms.

I've started to port over the current architect into Network.architecture.[architecture] as of 5946849

Cleaning this up next which will hopefully help with adding GPU Networks to Carrot

[luiscarbonell]

@christianechevarria I find it easier - conceptually - to imagine architect.[architecture] - as just an extension of Network.

Would you be cool with - or do you think it's easier to understand - creating networks with different architectures as Network.architecture.[architecture]?

For Example

let new = new Network.architecture.LSTM(365, 12) // Creates an LSTM with 365 input neurons and 12 output neurons.

As an additional note:

• We can leave the architect/architecture namespaces and classes for classes and functions that actually help create the network structure/topologies (i.e. NEAT or Instinct Algorithms). I find these to personally fit the term "architect" better since they are network designing algorithms.