ddrake / Integrated_Farm_Budget_Tool

Other
1 stars 0 forks source link

Final Projected Prices and Volatilities not Showing up Yet. #229

Open KelleyDrake opened 6 months ago

KelleyDrake commented 6 months ago

Just got back up to the Lake and checked my Champaign IL farm. It has not yet been updated for the final RMA price and volatility factors.

For corn for example IFBT has $4.65 and vol of .18 and the (est) is still in the title. Actual final from the RMA is $4.66 and .19. For beans IFBT has $11.55 and vol of .13 and (est) in the title. Actual final from the RMA is $11.55 and .15

ddrake commented 6 months ago

That’s odd, I’ll figure it out soon. Sent from my iPad

On Mar 3, 2024, at 1:26 PM, KelleyDrake @.***> wrote:



Just got back up to the Lake and checked my Champaign IL farm. It has not yet been updated for the final RMA price and volatility factors.

For corn for example IFBT has $4.65 and vol of .18 and the (est) is still in the title. Actual final from the RMA is $4.66 and .19. For beans IFBT has $11.55 and vol of .13 and (est) in the title. Actual final from the RMA is $11.55 and .15

— Reply to this email directly, view it on GitHubhttps://github.com/ddrake/Integrated_Farm_Budget_Tool/issues/229, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFH2MAAZ2JMMWJBSX3IHGDYWOIPPAVCNFSM6AAAAABEEILZEGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3DKNJWGYZDGMQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

ddrake commented 6 months ago

Yesterday evening, I checked that the script had run successfully on my local machine, and it had, but I failed to check the live server status. I checked that just now, and it had failed without any error message. So I ran the script manually, but the process was killed by the operating system before it could complete. This is the first time I’ve seen that issue with an IFBT script; usually it means it tried to allocate more than the available memory. It was killed while downloading a rather large daily file. I worked around it by running the locally-generated sql against the live database. In future, I will check both databases. I think the only long term solution is to upgrade the memory on the server (more $), but I want to think about it a bit more…

Sent from my iPad

On Mar 3, 2024, at 1:26 PM, KelleyDrake @.***> wrote:



Just got back up to the Lake and checked my Champaign IL farm. It has not yet been updated for the final RMA price and volatility factors.

For corn for example IFBT has $4.65 and vol of .18 and the (est) is still in the title. Actual final from the RMA is $4.66 and .19. For beans IFBT has $11.55 and vol of .13 and (est) in the title. Actual final from the RMA is $11.55 and .15

— Reply to this email directly, view it on GitHubhttps://github.com/ddrake/Integrated_Farm_Budget_Tool/issues/229, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFH2MAAZ2JMMWJBSX3IHGDYWOIPPAVCNFSM6AAAAABEEILZEGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3DKNJWGYZDGMQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

KelleyDrake commented 6 months ago

Ok. Sounds good. Just out of curiosity if we did choose to do the rolling downloads during discovery would that likely help or hurt the data requirements? I think we'd be pulling 17 x 2 or 34 data points each day.

Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message -------- From: Dow Drake @.> Date: 3/3/24 5:47 PM (GMT-06:00) To: ddrake/Integrated_Farm_Budget_Tool @.> Cc: @., Author @.> Subject: Re: [ddrake/Integrated_Farm_Budget_Tool] Final Projected Prices and Volatilities not Showing up Yet. (Issue #229)

Yesterday evening, I checked that the script had run successfully on my local machine, and it had, but I failed to check the live server status. I checked that just now, and it had failed without any error message. So I ran the script manually, but the process was killed by the operating system before it could complete. This is the first time I’ve seen that issue with an IFBT script; usually it means it tried to allocate more than the available memory. It was killed while downloading a rather large daily file. I worked around it by running the locally-generated sql against the live database. In future, I will check both databases. I think the only long term solution is to upgrade the memory on the server (more $), but I want to think about it a bit more…

Sent from my iPad

On Mar 3, 2024, at 1:26 PM, KelleyDrake @.***> wrote:



Just got back up to the Lake and checked my Champaign IL farm. It has not yet been updated for the final RMA price and volatility factors.

For corn for example IFBT has $4.65 and vol of .18 and the (est) is still in the title. Actual final from the RMA is $4.66 and .19. For beans IFBT has $11.55 and vol of .13 and (est) in the title. Actual final from the RMA is $11.55 and .15

— Reply to this email directly, view it on GitHubhttps://github.com/ddrake/Integrated_Farm_Budget_Tool/issues/229, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFH2MAAZ2JMMWJBSX3IHGDYWOIPPAVCNFSM6AAAAABEEILZEGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3DKNJWGYZDGMQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/ddrake/Integrated_Farm_Budget_Tool/issues/229#issuecomment-1975402199, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5TP6FWE2UUPWXYPIML22WTYWOZA7AVCNFSM6AAAAABEEILZEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGQYDEMJZHE. You are receiving this because you authored the thread.Message ID: @.***>