-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge JS's changes in #3
base: bgk
Are you sure you want to change the base?
Conversation
rupertnash
commented
Nov 15, 2016
- Corrected forcing term (d3q15.c)
- Fixed inconsistecy between forces and force densities (d3q15.c)
- Included forcing in initialization (Lattice.i)
- Fixed indexing error in PBCs (bc_pbc.c)
1. Corrected forcing term (d3q15.c) 2. Fixed inconsistecy between forces and force densities (d3q15.c) 3. Included forcing in initialization (Lattice.i) 4. Fixed indexing error in PBCs (bc_pbc.c)
Hi Rupe, Is this something I need to act on? I can't find any button for Cheers, Joakim On 2016-11-15 15:30, Rupert Nash wrote:
|
This is really just for a logical place to discuss this. I've done a preliminary test and if you set up your lattice with rho = 1, u = 0 and a non-zero force, then call initFromHydroVars() and updateHydroVars() you do not get zero velocity where the force != 0. I'm going to look at this more |
But neither should we - right? Is there not a correction term of On 2016-11-15 16:30, Rupert Nash wrote:
|
If you have rho and u, compute the equilibrium f, then compute rho and u from that, you MUST get back the same inputs up to machine precision. |
I am reasonably confident that my calc_hydro_site is correct (given that the "force" array stores a force density) |
In that case, yes, but in that case all the other routines should be
On 2016-11-15 17:20, Rupert Nash wrote:
|
Did you find any further leads? /J On 15/11/16 17:20, Rupert Nash wrote:
|