Forgot to ask - once I'm ready to switch from the weewx simulator to the actual Davis Vantage Pro 2 station, do I need to purge the simulated data before starting polling with real data?
I ask because that was how wview handled the transition between simulated and real data, in order to clear the database of sim-data. What do I need to do to purge the sim-data, if anything? I haven't found any reference to this transition in the documentation, and I suspect there is a "right way" and a bunch of wrong ways. I'd prefer not to stumble around doing the latter. Thanks!! Rod On Wednesday, 15 November 2017 04:28:02 UTC, Rod in Edm wrote: > > Ah, got it. This all sounds very promising !! > > I'll do a WeeWX install on the same box (after doing a backup of WView > data and config just in case) after reading your references. > > Thanks for the encouragement, Tom ... greatly appreciated !! Time to get > started reading :) > Rod > > On Wednesday, 15 November 2017 01:06:01 UTC, Tom Keffer wrote: >> >> Hello, Rod. >> >> Not surprisingly, I was also a long-time wview user before starting weewx. >> >> Mark Teel (the author of wview) was not a part of weewx, although, as you >> note, many of his design decisions influenced me. >> >> Because weewx uses the same schema as wview, moving over is a simple >> matter. Take a look at the transition guide >> <http://weewx.com/docs/usersguide.htm#wview_compatibility> in the User's >> Manual. >> >> The weewx install will not write over any wview resources. Indeed, there >> is no reason not to use the same box that wview is on. Because weewx is >> written in Python, rather than C, it actually uses *more* resources than >> wview, but it's still a small footprint. Many users have it running on >> Raspberry Pis or NAS's or old routers. >> >> Read through the User's Guide <http://weewx.com/docs/usersguide.htm> >> then give it a go. >> >> -tk >> >> On Tue, Nov 14, 2017 at 4:53 PM, Rod in Edm <[email protected]> wrote: >> >>> I've been a WView weather display program user since about 2010, and >>> while a bit dated looking UI-wise, found it sufficient for my needs. Its >>> installed on an AMD MB-based computer, with 240GB SSD, and running under >>> Debian Linux. Its connected to my Davis Vantage Pro 2 weather station via >>> Davis' USB data logger cable/dongle. I've been slow to upgrade the OS >>> (currently running Debian Jessie, but left WView running Wheezy code). >>> >>> But its become clear that WView's days are over (or nearly so) - it >>> hasn't been updated for a long time and support for it appears non-existant. >>> >>> I'm not complaining - for a freebie piece of software, it was great, its >>> run largely unattended, and its author deserves a lot of credit - Thanks, >>> man ! >>> >>> Anyway, I've been looking into WeeWX as a replacement if for no other >>> reason than this huge and active user group. Reviewing the configuration >>> process and code, it looks a LOT like WView in many ways, meaning I might >>> even be able to import my archived 2+ years of WView data into WeeWX - not >>> an absolute necessity but keeping that data for reference would be nice, >>> and on the surface it at least looks feasible. >>> >>> My questions are these: >>> >>> Can I install WeeWX onto the same Debian box, still running Jessie, >>> without disturbing WView? Will the installation overwrite any >>> WView-critical files or dependencies? I realize I'll have to shut down >>> WView so I can start up WeeWX (since they both want access to the same data >>> source, the Davis USB cable port) ... but is there any reason to worry >>> about cross-interference up to that point? I'd prefer not to irreparably >>> corrupt the WView data if I can avoid it. >>> >>> I can always just leave the WView installation alone and do a totally >>> from-scratch install of WeeWX on a RPi3 / SSD combo, transfer old data >>> across (assuming its importable), get everything ready on the Pi before >>> shutting down WView and moving the Davis cable from one box to the other - >>> and there are lots of reasons to consider that solution better anyway, from >>> many angles ... and I may do this anyway since WeeWX doesn't appear to need >>> the power or resources of the WView box. Re-using the WView box isn't a >>> requirement for me. But is it safely possible? >>> >>> As an aside, was the WView programmer a key part of launching WeeWX, or >>> vice versa? The similarities in code and UI are pretty numerous. >>> >>> Thanks for any input. >>> Rod in Edm >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weewx-user" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
