Category:Cumulus MX: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
m
When I am happy to stop using MX, I type '''Control + C''' into that MX command window on my PC and MX closes.
 
One more lessonObviously, you cannot have Cumulus 1 and Cumulus MX running at same time, accessing same weather station. If you (like I was to begin with) are just experimenting with MX you may sometimes run one flavour (say MX) and sometimes the other (Cumulus 1). Each time you swap, you must copy all the updated log files from the ''just used'' data folder to the data folder you are ''about to use'' when you close one favour before you start the other flavour, or you must have both executables in same top level folder to force them to share the data folder. If you don't do either of thosePlease alternativesnote, various derivatives (e.g'''today.ini''' Chillis Hours)a willspecial becomecase, wrongthe andtime-stamp youline mayhas havea conflictingdifferent rowsformat in dayfile.txtCumulus 1 (becauseC1) itsand contentMX; iswhile generatedMX fromcan what that flavour saw when it was runningread the previousformat day)that andC1 generallyuses, thisC1 willcannot beunderstand particularlythe evident in any weather parameterformat that variesMX a lot likeuses. windRemember vector[[today.ini]] Itdetermines alsowhich affectsstored anyentries thatin relythe onweather averagingstation (temperature,console windneed run,to rainbe rate)read asto these"catch-up" areand calculatedit biasedalso towardsholds the actualvarious times whenfigures that flavourwill ofinform Cumuluswhat wasgets actuallystored running,in so[[dayfile.txt]] you can have issues if you runat the 2end flavours in different folders/devices as ifof the other does not existday.
 
If you don't do either of those alternatives, various derivatives (e.g. Chill Hours) will become wrong and you may have conflicting rows in dayfile.txt (because its content is generated from what that flavour saw when it was running the previous day) and generally this will be particularly evident in any weather parameter that varies a lot like wind vector. It also affects any that rely on averaging (temperature, wind run, rain rate) as these are calculated biased towards the actual times when that flavour of Cumulus was actually running, so you can have issues if you run the 2 flavours in different folders/devices as if the other does not exist.
I have some batch scripts that Cumulus initiates, and a number of Cumulus templates, and in my case I had to be happy these were working before I stopped using Cumulus 1, and got MX as the flavour that auto-started on switching on my PC.
 
I have some batch scripts that Cumulus initiates, and a number of Cumulus templates, and in my case I had to be happy these were working before I stopped using Cumulus 1, and got MX as the flavour that auto-started on switching on my PC. I also use output modifiers on a lot of the web tags I use in my custom web pages and it took me a long time to work out the necessary changes to get these templates edited so that MX could process them and produce the web page content I wanted. I am not going to explain all the problems nor give the solutions, because you probably don't have web pages as complex as mine.
 
=== Success ===
5,838

edits

Navigation menu