Own Models Applied {OwnModelsApplied}

Principle

Apply what I invest resource on to my own problems. Each page in this group should correspond to a personal problem or set of problems. The process and its tools stay within the wiki (e.g. as recipes) in order to maintain coherence and move for a solely descriptive wiki to a more dynamical system.

Process

1. list problems
2. map problems
3. apply the cheapest solver, rate results of solvers
   1. if there is no satisfying result
      1. if all solvers has been used
         1. map the problem differently and go to 2
      2. select a more costly solver and go to 3
4. go back to step 1 and update

Result

Tools

Problems

• Needs
• SelfDiscipline
  • i.e. ToDo and projects

Organized models

• ExtendedLayeredModel (relative to each other)

Solvers

• exploration in time
  • Seedea:Research/PhylogeneticFlowProgramming
• generation of solution
  • Seedea:Seedea/BackEnd

Remarks

• degrees of freedoms or dimension of explorations have a non negligible cost
• new solutions are not necessarily required, what is new for a problem holder is most of the time not entirely new for others
  • in such situation the problem solving can be replaced by a search
  • overall semantics and hermeneutics can be overrated
    • at least by delegating cognition from the solver to the rater

Inspired by

Having to navigate in a crowded street of Madrid during the winter holidays and wondering how my models could make me more efficient that other wanderers.

To do

1. make Template? based on Process, LeveragingRandomness and new requirements from this very todo list
2. simplified the feedback process
   1. i.e. usage itself shows limitation of the tool and its underlying model, yet as both should be updated the usage should be pursued while taking into account such required modifications
   2. consequently each applied models should link back to its source model
      1. e.g. LeveragingRandomness From Wiki.ToDo#LeveragingRandomness