add C14 parameter to standard output#39
Conversation
|
Are you using the net we have exchanged on Slack? I have compiled and run your branch but I got a bit of an odd result in the first time-step. I mean this shockingly low value of |
Mikolaj-A-Kowalski
left a comment
There was a problem hiding this comment.
LGTM!
The only thing I am worried about is this odd value I got in the 'corner'. However I would doubt it is related to the output writing itself.
Otherwise just a question!
yes exactly.
I get the same worrying value for the first time-step. I don't know enough about the case and the net, but probably it gets initialized from a velocity field far from what the net has every seen (maybe from rest?). Then it doesn't know what to do |
|
If you can have a glance so we can merge promptly to keep the momentum going ;-) (totally not because the batching PR I will be opening soon is rebased on top of this one 😅... ) I am a bit worried about this odd C14 value at the start, but with all likelihood it is not related to the output. So we should track it via a separate issue. |
I created a separate issue #41 and assigned @adconnolly for now. I agree that we need to know where this comes from. |
adconnolly
left a comment
There was a problem hiding this comment.
I'm also a little confused about the iC14 = 0 discussed in a resolved comment, actually I'm confused on why all the variables' indices are set to 0 in that file, but I'm happy to assume it is just some goofy initialization/declaration thing. In any case it doesn't seem related to the bigger issue of the weird values, but the new PR can address that. So I agree with consensus to merge and keep the ball rolling - but not because the batching PR is rebased on top of this one, Mikolaj has made that clear :)
Addresses #37 and adds the C14 parameter to the standard output. I've tested this using the BOMEX standalone case with and without ML: