Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
PH3110 BSc projects / PTD | ||||||||
Line: 33 to 33 | ||||||||
Other | ||||||||
Added: | ||||||||
> > |
| |||||||
-- Pedro Teixeira Dias - 18 May 2021 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
PH3110 BSc projects / PTD | ||||||||
Line: 32 to 32 | ||||||||
Other | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
Changed: | ||||||||
< < | -- Pedro Teixeira Dias - 2 April 2021 | |||||||
> > | -- Pedro Teixeira Dias - 18 May 2021 | |||||||
Comments |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
PH3110 BSc projects / PTD | ||||||||
Line: 30 to 30 | ||||||||
A random walk is an example of a Markov chain process. | ||||||||
Added: | ||||||||
> > | Other
| |||||||
-- Pedro Teixeira Dias - 2 April 2021
Comments |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
PH3110 BSc projects / PTD | ||||||||
Line: 28 to 28 | ||||||||
One of the initial goals of the project could be to establish that the random walk used in the project does conform to the expected statistical properties of a truly random walk: eg that the expectation value of the distance travelled by particles after n steps is zero, and that the expectation value of the distance squared is n (or, equivalently, that the rms distance is √n). Students could compare the standard 2D random walk (where particles can only move up/down/left/right) vs a random walk where, in addition, 4 diagonal movements are also allowed (NW, NE, SW, SE). The latter is preferred for the nuclear fission project because it means that in the finest chessboard configuration (where the four nearest-neighbours of an M (F) cell are all F (M) cells) a neutron can move to either a F or M cell. The former means that in this same pile configuration the neutron will always move from to a cell of different type from the type of the cell in its initial position with 100% probability: i.e., always from M to F, or from F to M. | ||||||||
Changed: | ||||||||
< < | -- Pedro Teixeira Dias - 18 March 2021 | |||||||
> > | A random walk is an example of a Markov chain process. -- Pedro Teixeira Dias - 2 April 2021 | |||||||
Comments |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
PH3110 BSc projects / PTD | ||||||||
Line: 20 to 20 | ||||||||
Changed: | ||||||||
< < | -- Pedro Teixeira Dias - 14 Jan 2021 | |||||||
> > | Random walksOne of the projects offered involves particles doing a random walk in two dimensions. More information about random walks (and an animation of a 2D random walk) can be found in the following: One of the initial goals of the project could be to establish that the random walk used in the project does conform to the expected statistical properties of a truly random walk: eg that the expectation value of the distance travelled by particles after n steps is zero, and that the expectation value of the distance squared is n (or, equivalently, that the rms distance is √n). Students could compare the standard 2D random walk (where particles can only move up/down/left/right) vs a random walk where, in addition, 4 diagonal movements are also allowed (NW, NE, SW, SE). The latter is preferred for the nuclear fission project because it means that in the finest chessboard configuration (where the four nearest-neighbours of an M (F) cell are all F (M) cells) a neutron can move to either a F or M cell. The former means that in this same pile configuration the neutron will always move from to a cell of different type from the type of the cell in its initial position with 100% probability: i.e., always from M to F, or from F to M. -- Pedro Teixeira Dias - 18 March 2021 | |||||||
Comments |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
PH3110 BSc projects / PTDIntroductionThis TWiki topic collects some information that is relevant to the numerical simulation projects for PH3110 that are supervised by PTD.Program structure / FlowchartWhen developing a new computer program, it is essential to plan the main structure of the program before starting to actually write any code. Good code is modular and well documented. One key tool to help plan the structure of a computer program is to prepare a flowchart for the whole program, highlighting the main tasks/algorithms that the code will perform and the order they will be performed in. Separate additional flowcharts can also be used to provide further detail on certain parts of the code (eg if they are quite complex, and need a flowchart in their own right). The following web pages introduce the basic ideas and conventions behind computer program flowcharts, with examples:
Comments |