Hi Julie I will get some example input files for this situation when the model crashes, but I won't have the output roadcast file because...er...well the model crashes :)
Regarding your comment that the input obs file end timestep should be the same as the input forecast start timestep ; how does the coupling stage of the model work in this case ... i.e. in the example you gave, there's no overlap of obs and forecast and so there's no way for the model to learn from the forecast biases. Maybe I'm missing something. Regards Iain -----Original Message----- From: Julie Prestopnik [mailto:[EMAIL PROTECTED] Sent: November 12, 2007 12:19 PM To: Iain Russell Cc: [email protected] Subject: Re: [Metro-developers] METRo crashes when obs and forecast start times are the same Hi Iain. I'm not sure if I'm interpreting your message correctly or not. It sounds like you want the input observation file and the input forecast file to start at the same time. For example, having them both start at: 2006-07-12T00:00Z But instead, METRo wants to have the first input forecast time the same as the last input observation time. So, for example, my observation file would start at 2006-07-12T00:00Z and end at 2006-07-12T12:00Z. And, my forecast file would start at 2006-07-12T12:00Z and end at 2006-07-15T23:00Z. METRo wants to get the model going by using input observations to start with and then use the forecast information following the observations to help determine the roadcast. The issue that I reported back on April 6th, was a different situation. We only had one hour of forecast data, but METRo requires at least two hours of forecast data. I hope this has helped. Also, if you want help in reproducing behaviour, it's always helpful to attach all of your I/O files (observation file, atmospheric forecast file, station configuration file, output roadcast file) and the command line that you're using. That way we can test the exact problem that you're having without having major differences. Let us know if you have any further questions or need any assistance. Thanks, Julie Iain Russell wrote: > Hi > > We have found that METRo crashes when both the input observation file > and the input forecast file start at the same timestep. > > Operationally we are running version 2.1.1, but we also did a test with > the latest stable release and got the same result. In order to > circumvent the problem we are capturing more historical forecast data > than observation data so that our 2 input files never start at the same > time. > > A similar-looking issue was reported on April 6th 2007 by Julie > Prestopnik ; but I'm unsure if the case that Julie reported and the one > I'm reporting here are related in any way. > > Can someone do a test to see if you can reproduce the behaviour I'm > reporting here ; make the first timestep in the input observation file > and the forecast file the same times. > > Thanks > Iain > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > METRo-developers mailing list > [email protected] > https://mail.gna.org/listinfo/metro-developers _______________________________________________ METRo-developers mailing list [email protected] https://mail.gna.org/listinfo/metro-developers
