Serial_Player_Capacitors

Serial capacitors like source in a game of dice.

Description

In this program 10 friends play with 10 dice with 10 sides for 10 times in the forward verse and for 10 times in the behind verse.
PC obtain a vector of classification of 10 elements in the forward verse and of 10 elements in the behind verse.
The vectors in output are:
1. DELTA POINTS = NOT no = POINT OF LEFT CURRENT = PSX
2. forward points = choice = point of right up current = pdx/2
3. behind points = nochoice = point of right down current = pdx/2
4. total points = no = point of right current = pdx
The 1° vector: 10 difference of forward-behind verse.
The 2° vector: 10 forward verse.
The 3° vector: 10 behind verse.
The forwards and the behinds are numbers of points of the 10 players. The input is the number of steps (the time) of each player-soluction in the double verse.
The 4° vector: the sum of forward point with behind point.
The strategy used is the same of the soccer-tourney with 20 teams but in this case teams are 10 (the players) and each player play a game with himself because is indipendent to other friends. The winner is the bigger number of steps. Is an inverse winner-logic.
The 5° vector: are 10 numbers of the current-points:
DELTA POINTS + total points = yes + no = point of current
The sum of the 10 current-points is the number of circuitation:
2 forward points = 2 choice = circuitation of current = sum (yes + no)
The criterion used to me for the classification of forward-behind verse is a combination of number of die and number of side and number of steps. This criterion (it obtain 2 vectors of 10 elements in the range 1-10) isn’t the current-input (output of the players-steps) because the current-input is the number of the steps: for the classification are used 3 input and for the current is used only one input (the time, steps). The five vectors and the circuitation-number are obtained with the forward-steps and the behind-steps of the 10 players. Classification is with 3 input (two space and one time) and the current is builded with only one input and this number is the time-variable of the steps and bigger number is a superior quantity in the current-function (bigger number of steps is a bigger current function).

Acknowledgements

The author wishes to acknowledge the following in the creation of this submission:
diceN_classification

• MATLAB release: MATLAB 6.1 (R12.1)

[PXlab]

zero downloads and one comment.... ihih... I haven't used the formula of differential equation.... I is the current in function of the time and C the capacity and V the voltage and T the time..... "d" is the symbol of derivation..... dV/dT .... umh.... like A/B where A is dV and B is dT..... wow...... in future version I'll speack of this formula.... magic formula ;)

[Anon]

No, a capacitor indipendent to time is still a capacitor with time. Imagine two capacitors walking side by side. Even without time the second walks faster than the first because their relation is point in the half. If three capacitor, this gets complicated. Because then point of half becomes point of half by half. Yours assumption is wrong. Think of relativity ... capacitor 1 divided by 2 and 3. Realize all of them are equal but with different speeds they become different. Negative velocities will remain as long as you retain your position relative to capacitor 1 2 or 3. You think you know capacitors, but you know only one. You have to beware, because all are different, some dangerous some friendly. Finding a formular of it requires classification in good or bad. But I'm sure, you find the answer. But beware, some female capacitors can be very attractive, and their boyfriend capacitors don't like see you after them.

[PXlab]

I=C*V/T
Q=C*V
I=Q/T
...
V=X/T
...
V=I ... velocity is current .... meter = Ampere * second
X=Q ... length is charge ..... meter = Coulomb
T=T .... time is time ........... second = second
...
in the program where there is “current” word is possible write “velocity” word and it is the same thing: the point of current with 10 elements is a point of velocity of 10 elements and the circuitation of current is a number of sum like the number of sum of the velocity-circuitation

[Hal 9000]

That's all well and good, but there is nothing in your code that would suggest you are doing any kind of legitimate "simulation" of either electrical circuitry or newtonian physics. All your code ever seems to contain is copious if/else statements, questionable algebra, and a bunch of fprintf statements. It's misleading of you too sell this as any kind of simulation or to use terms like "current" when you really aren't modeling true circuitry.

[PXlab]

My simulations are a way, newtonian physics is a strategy of the ‘600; to say letters or to say electrical capacitors or to say teams is the same thing (2=0 of the letter-liberty) becuase my models are a triple point; if elseif are controls, very important controls, and my style use if elseif; the algebra is ok and fprintf command is a video output.

[Gavrilo Bozovic]

Okay, even without entering the subject of the actual calculations, this is VERY BAD coding.

Marco, once again, innumerable imbricated for/while/if-elseif structures can only lead to an incomprehensible code, bound to make errors and be impossible to debug.

Look at the codes that have good ratings here, and try to learn from them.

Then, it's true that you should also take some math classes regarding your assumptions..

[PXlab]

6 commands: clc fprintf disp randperm zeros sum
20 for
2 while
28 if elseif
why bad code?
A program, in this way, is a book and to read it is simple, I can not use a manual, is necessary to know only 6 commands of the language, this is a logical structure of visible numbers. My fantasy say to me of your programs-style, a programmation style with sophysticated commands but I can’t see your programs; anyhow isn’t a better style your method if is so, not for me, is an interpretation of the object-function, of the purpose. I think this and in my mind is error to say bad code to a functional code.

[Gavrilo Bozovic]

using few commands is NOT a sign that your code is good!

you could write a whole OS in brainfuck, which is a language that has 8 operands, and it would work, but it would be MESSY, and it would be IMPOSSIBLE TO DEBUG.

The fact that you use few commands only shows that you do not know enough commands to make an efficient program.

[PXlab]

In to my purposes code is efficient, I know few commands but this isn't equal to write bad codes; the loops, the controls, the mechanism, the logical numerical structure are ok and I can see the structure without to know a lot of commands. I think your purpose is different. The programs are books and the programs-executions are films; in a book I must read, book is static, with a film is the film in movement; the movements of the program are ok, and this movements are a book-basis with a style of the writer. In my memory-brain there are few commands because the book style is for loops while loops and if elseif controls and I can see the numbers.

[Gavrilo Bozovic]

One thing is certain: if you keep claiming that your code is good, even if your submissions have an average rating of ~1, you will NEVER get better.

To get better at something, you first have to admit that what you do is not perfect..

[alain boyer]

 

[V. Poor]

Poor.

[pitta]

 

[James]

 

[C]

 

[Ripley]

 

[Bishop]

 

[newt]

 

[Hudson]