Effective storing and calling of directions

• Internal conversion of vecs to x, y, z in order to efficiently store inside shape_array? -> better smaller size than fast calling of vecs?
• remove convert_all in simulations
• raise Warning only if someone stores different info in a similar direction key, no warning for same info (enables faster calling)

• How to treat pixels regarding the conversion?