Original release topic

[PaulMy]

Dropped in cumulusutils.exe v.2.1.0 yesterday and all is good this morning.

Also agree with Piotr to your question on reading dayfile.
There is a dayfile editor in Cumulus.

Thanks, and enjoy,
Paul

[HansR]

Thnxs Piotr and Paul.
I see a dayfile viewer, not an editor @Paul.

[PaulMy]

in Cumulus 1

Enjoy,
Paul

[Phil23]

Hi Hans,

Re The Graphs module.

Just wondering if you can rework it to produce EVT charts similar to the Daily & Monthly rain.
Presume this would just require a duplication of the existing code, but picking up the EVT value from the dayfile as well as rain.

Don't know whether to suggest separate charts, or to overlay it on the existing rain charts.

I know EVT is a derived value, but it is of interest to anyone involved in cropping & growing pastures & is effective in helping with best irrigation rates.

Cheers.

Phil.

[HansR]

@phil:
I'll look into it. Not the coming three days, after that I'll have a look.
Cheers, Hans

[hills]

Hi Hans, would it be a difficult change to make the pointer point to todays prediction if forecasting is activated?

I have implemented this on my FWI with a fairly messy awk and sed script to replace the current value with the predicted value and recalculate the position percentage, but obviously that'll only work on Linux implementations and I'm sure will break with future upgrades.

Cheers

Phil

[HansR]

@hills:
Hi Phil,

I see what you did and I have to appreciate the skills and inventivity of awk and sed scriptwriters getting there. I had never thought the output would be reworked like this although the other phil (phil23) did something like that on the graphs module, also well appreciated from the adaptational point of view

To be honest, I deliver the output in the way I do, because I think that is the way it should be regarding the science behind the code. Wrt the graphs I made clear that the thick line actually would insinuate a statistics display of a a standard deviation or alike which it isn't. Wrt pwsFWI I always made clear that the only valid value - for me, and I designed the thing - is the last value calculated with the measurements. So that is the value calculated on the basis of the last registered day in dayfile.txt. It made me resist to prediction in the first place - and in a way I still do. Although I like the addition, won't deny that: it gives a quick overview of the past and future weather and fire danger

But to make the current value a predicted value goes too far, I think.

1. The calculated value remains the only valid value for the pwsFWI;
2. If a predicted value of pwsFWI could become current there would be a difference between installations and therefore an impossibility to easy compare.

Those who access the page with the pwsFWI info should know what they get.
So, I will not make a prediction value the current value. I hope you will accept and appreciate my point of view.

If you decide to carry the change you made - I will not change my software to prevent you to do that - I would at least appreciate a NOTE somewhere saying what you did and maybe even that we agreed to disagree on this issue.

Cheers, Hans

[hills]

Hi Hans

Absolutely no problems at all and thanks for spending the time explaining that.

I guess my reasoning was I'd like to draw the viewers attention to today's prediction rather than yesterdays result as that is what they should be acting upon, in much the same way my main site highlights a prediction for todays weather rather than pointing out what yesterday's weather was.

While yesterdays information is there and of interest, I believe todays prediction is more important to be highlighted. I'd hate for someone not to take appropriate action because they viewed yesterdays low fire danger instead of todays predicted high fire danger.

However as you wrote this fine code I am more than happy to abide by your decision.

Cheers and thanks again

Phil

[beteljuice]

@hills

If you are using the betejuice display option ...

Here is a 'patch' that should do what you want
... of course if Hans ever changes the scale It will be incorrect.

Ensure your page is loaded with Jquery
Then (preferably in the <head>) put this in your page:

Code: Select all

<script>
// forecast pointer patch - beteljuice
// invoke when first loaded on page #### wait until JQuery says everything ready
$(function(){
var rodney = $('#fwi_data').find("tr:eq(6)").find("td:eq(6)").html();
var boycie = rodney.replace(',','.');
var terry = (boycie / 10 ).toFixed(2);
var delboy = '\
<div id="moveit2" style="padding: 0px; margin: 0px; position: absolute; left: 0px; bottom: 30px; width: '+terry+'%;">\n \
<div id ="pointer2">&#9660;\n \
<div id = "fv1"> '+rodney+' </div>\n \
</div>\n \
</div>\n';

$(".fwi_key").find("tr:eq(0)").find("td:eq(0)").append(delboy);
});
</script>

<style>
#fwi_content #pointer2{
  position: relative;
  float: right;
  left: 19px;
  width:38px; height: 18px;
  font-size:25px; font-weight: bold; font-family: arial;
  text-align: center;
  text-shadow: 0 0 4px #000000;
  color: moccasin;
}
#fwi_content #fv1 {
  position: relative; top: -40px;
  color: black;
  font-size: 12px;
  text-shadow: none;
  font-weight: bold;
}
</style>

Let me know if you use it (and it works !)

NB: Only to be used together with 5 day forecast !!

[hills]

Wow!! Thanks, will do!

[HansR]

[beteljuice]

... better than your code being trashed modified Hans

... and no doubt Henry Ford thought the same when someone put bumpers on one of his cars

[HansR]

[hills]

... better than your code being trashed modified Hans

... and no doubt Henry Ford thought the same when someone put bumpers on one of his cars

OI!! I resemble that remark!

Oh and for the record... I haven't touched Han's code, I just modify the page it creates after the event.

[HansR]

I get it guys, no hard feelings
But, @phil,

I haven't touched Han's code, I just modify the page it creates after the event.

That's also my code
Anyway, I can.live with it.