Report Observation times out
Hi,?
Just to let you know, I cannot report an observation this morning (10.00UT) from OW.? (W7 and W10). The operation does nothing other than ("not responding") and times-out after a short while.?
Thanks for all the help keeping these systems running.
Cheers Tim
Oxfordshire
|
Re: Question about the maps on OWC and OW
Hi Vince,
What you see is the way OW and OWC show you the effect of altitude correction. You actual cord position is close to the shadow edge. The small difference between OWC and OW plots are likely a result of either rounding or perhapse if you have manually entered your altitude in OW dekstop and it differs from the automatic altitude that OWC is getting this could also explain the small difference. Regardless your actual chord position is close to the edge of the shadow.
> An finally,? what do I, as an observer need to do to make everything line up correctly?
Nothing. This is not meant to line up correctly. The real qustion is how you can interpret the white line and how you could select an observing location at a chord that you want.
Let me start with the white line in OWC. What you see is a fast way to plot altitude corrections. I hope at some point to plot the entire path altitude corrected (which will result in everything lining up, but the shadow bath wiggling along) but this is not how it works now. Instead OWC plots the non-altitude corrected path - the green, blue and red lines of the path. When you pick a loction to observe from, OWC will query online the altitude for this location and will apply altitude corrections. Then it will plot the while line that shows you where your actual altitude corrected chord is positioned after the corrections. To read this, you simply need to look at where is the white line drawn relative to the blue, green and red lines of the non-corrected path.
In your case the white line tells you, your actual cord is very close to the edge of the shadow. OW Desktop's plot only shows you the position of the altitude corrected chord and again it is very close to the edge of the shadow.
Now looking at the GoogleMap on OWC you can see that the altitude correction pushes your cord UP and away from the center line. If you want to have a station and a chord that is close to the center line, what you need to do is to select a location on the map that is DOWN from your current position, about 0.7 half path widths. This will place you close to the center and using the white line and an indicator you will be abel to confirm exactly where this cord will be located. You can move it a few time until you are happy with the resulting altitude corrected chord.
Of course if this is a fixed observatory you can't move your chord, and in this case you just need to know that your fixed observatory location is close to the edge of the shadow, rather than beeing deep inside the shadow, as it appears in the non-altitude corrected path on GoogleMaps.
I hope this makes sense.
Hristo.
On Sunday, April 21, 2024 at 09:10:35 AM GMT+10, V Sempronio <vastronomy@...> wrote:
(166404) 2002 NP41 occults TYC 5061-00646-1 OW announced (black highlighted event) that a change had occurred to the above event. I selected it and noticed my selected? observing location is very near the outer edge of the shadow path.  I then looked at the event in OWC and sure enough, there was an update on the 19th. the OWC event maps matches what I see when I invoke the OW "save google earth KLM" feature, and my observing location on both show up half way between the center line and the edge of the shadow path. The path graph in both OW and OWC show my position at the edge of the shadow path. What is going on here? Is it an altitude issue? Also, what is the white line and why does it point from my observing point to somewhere (arbitrarily?) on the white line?  An finally,? what do I, as an observer need to do to make everything line up correctly? Vince
|
Question about the maps on OWC and OW
(166404) 2002 NP41 occults TYC 5061-00646-1 OW announced (black highlighted event) that a change had occurred to the above event. I selected it and noticed my selected? observing location is very near the outer edge of the shadow path.  I then looked at the event in OWC and sure enough, there was an update on the 19th. the OWC event maps matches what I see when I invoke the OW "save google earth KLM" feature, and my observing location on both show up half way between the center line and the edge of the shadow path. The path graph in both OW and OWC show my position at the edge of the shadow path. What is going on here? Is it an altitude issue? Also, what is the white line and why does it point from my observing point to somewhere (arbitrarily?) on the white line?  An finally,? what do I, as an observer need to do to make everything line up correctly? Vince
|
OccultWatcher v5.4 Released
Hi All,
I realeased a new update to OccultWatcher desktop today that I believe will fix the problem that I think a very small number of users may have been seeing.
The issue occurs if the default Windows Reginal Settings date separator has been changed from the default '/' to something else, e.g. a '-'. In such a case OW was not able to identify if a prediction update sent by OWC was actually an update and would ignore it. If you have been affected by this issue I recommend that you purge your OW database after you update to this latest version. Note that this update only fixes the problem where the date separator has been changed. If you have not changed your date separator in Windows you don't need to purge your OW database aftert the update.
This release also introduces functionality that will push your locally stored Saved Sites in OW to OWC which you will be able to see and edit from your user profile:
Please note that this is only one-way sync and the intention is to migrate your OW Desktop sites to OWC as I hope to soon release an extended filtering/search functionality that works fully on OWC (web browser only) and can find events to observe based using a more extensive criteria including distance from center line or shadow, probablity to observe occulation and others.
I'll annouce more on this OWC improvement once there is something more widely available.
Regards,
|
Hi all,
As you have probably noticed there have been more frequent OWC outages lately which I am aware of, caused by server issues.
I'll need to investigate all this further potentially with my service provider.
The server appears hanging right now and I won't be able to reboot it until I get back home about 7 hours from now.
Cheers,
Hristo.
|
Re: Looking for Beta Testers for new OWC Event Search
I would be happy to participate Thanks Suhas
On Mon, 4 Mar 2024, 16:57 hristo_dpavlov via , <hristo_dpavlov= [email protected]> wrote:
Hi All,
I have been working on a new search functionality on OWC to make the bulk of untagged events to be searched in a better and faster way.
I am looking for users who are interested in helping with Beta testing this new search mechanism. It would be nice to have a mix of active observers as well as more casual ones.
If you are interested to participate please contact me directly.
I expect to have something ready to testing within the next few weeks.
Cheers, Hristo.
|
Re: Looking for Beta Testers for new OWC Event Search
Hello Hristo, although I am a beginner in using OWC, I would like to participate.
Carlos Botana
|
Re: Looking for Beta Testers for new OWC Event Search
Please, count with me.
Carlos
El 04/03/2024 a las 12:26,
hristo_dpavlov via groups.io escribió:
toggle quoted message
Show quoted text
Hi All,
I have been working on a new
search functionality on OWC to make the bulk of untagged
events to be searched in a better and faster way.
I am looking for users who
are interested in helping with Beta testing this new search
mechanism. It would be nice to have a mix of active observers
as well as more casual ones.
If you are interested to
participate please contact me directly.
I expect to have something
ready to testing within the next few weeks.
Cheers,
Hristo.
|
Looking for Beta Testers for new OWC Event Search
Hi All,
I have been working on a new search functionality on OWC to make the bulk of untagged events to be searched in a better and faster way.
I am looking for users who are interested in helping with Beta testing this new search mechanism. It would be nice to have a mix of active observers as well as more casual ones.
If you are interested to participate please contact me directly.
I expect to have something ready to testing within the next few weeks.
Cheers, Hristo.
|
Re: Bug in RIO/TNO and Lucky Star "notification" windows
I have noticed these as well but I only seen them while I was using the application and I haven't seen them stacked up if I walk away. Still I have no idea why we have to see them at all.
Vince
|
Bug in RIO/TNO and Lucky Star "notification" windows
Every so often, OW puts up a couple of windows on which you have to click OK to confirm you will continue to send your results from Lucky Star and RIO/TNO predictions to those groups.? There is a timer so you have to read the text for 30 seconds before you can click OK.
So far so good.? However, I came back from a 3-week trip and there were over 100 of these message?windows stacked up on my Windows desktop that I had to click through to get rid of them.
I'm sure this was not the intention in the original design!
Hristo could you take a look at this please?? I've had it happen before, but not this many.
Thanks! Ted B.
|
OccultWatcher v5.3 Released
Hi All,
I realeased a new update to OccultWatcher desktop today which tries to address an issue where sometimes updated predictions on OWC are not picked up correctly from OW.
There are two changes in this release.
Firstly I have made a change that would hopefully make the issue occur a lot less frequently. Having said that it is evident that there is a problem and I have been
unable to track it down so the root cause has not been fixed, but as I
mentioned I hope that it will occure a lot less frequently in this
version.
Secondly I implemented local logging where log files will be kept for the last 30 days so if someone does experience the problem again, hopefully the log files will help me identify the problem. If not I may need to add more logging, release a new version and keep hunting for it.
If you would like to help to track down the problem faster, please contact me directly and I will explain to you how you can revert my first change to make the issue keep happening at its current rate, which hopefully will be noticed earlier and I'll have the opportunty to look at some log files earlier and hopefully fix it sooner.
If anyone notices an event in OW that has not been updated with the latest prediction from OWC even after a repeated synchronisation, please contact me stright away so I can gather more information sooner.
Thanks for the understanding while trying to track down the bug.
Regards, Hristo Pavlov.
|
Re: Occultwatcher software: selection filter by probability
Yes, .. will do that way but getting hundreds of events from many feeds (growing in number .. which is very good!) that even if ranked high they will have 0% probability for specific sites... so making very inefficient the my-event choice for further preparation and observation commitment.
Therefore, if someone from the Occultwatcher development team is willing to take this request for new feature request, I guess this tool will be a world class planning tool. Thanks Claudio and everyone for this good discussion. Regards
Il giorno lun 15 gen 2024 alle ore 08:45 Claudio Costa < carocicosta@...> ha scritto: Paolo, you can add the column “Probability” and sort accordingly, even if you cannot filter. Claudio ? ? Rank is an absolute parameter based on confidence of data available while probability is related site specific. So it is really useful to filter by probability rather the rank. ? Il giorno lun 15 gen 2024 alle 07:29 Claudio Costa <carocicosta@...> ha scritto: Paolo, in “Configuration” you can filter by Rank Claudio Costa ? ? Hello group, is there any chance to get filtered the event list by the probability field? Thnaks, Paolo F
|
Re: Occultwatcher software: selection filter by probability
Paolo, you can add the column “Probability” and sort accordingly, even if you cannot filter. Claudio ? ? Rank is an absolute parameter based on confidence of data available while probability is related site specific. So it is really useful to filter by probability rather the rank.
toggle quoted message
Show quoted text
Il giorno lun 15 gen 2024 alle 07:29 Claudio Costa < carocicosta@...> ha scritto: Paolo, in “Configuration” you can filter by Rank Claudio Costa ? ? Hello group, is there any chance to get filtered the event list by the probability field? Thnaks, Paolo F
|
Re: Occultwatcher software: selection filter by probability
Rank is an absolute parameter based on confidence of data available while probability is related site specific. So it is really useful to filter by probability rather the rank. Thanks?
Il giorno lun 15 gen 2024 alle 07:29 Claudio Costa < carocicosta@...> ha scritto: Paolo, in “Configuration” you can filter by Rank Claudio Costa ? ? Hello group, is there any chance to get filtered the event list by the probability field? Thnaks, Paolo F
|
Re: Occultwatcher software: selection filter by probability
Paolo, in “Configuration” you can filter by Rank Claudio Costa ? ? Hello group, is there any chance to get filtered the event list by the probability field? Thnaks, Paolo F
|
Occultwatcher software: selection filter by probability
Hello group, is there any chance to get filtered the event list by the probability field? Thnaks, Paolo F
|
Re: Feature enhancements to Station Sorts
Hi Vince,
I think that the chord offset, or the distance to the centre line from your Home location measured on the fundamental plane, can be added as a column in the main list of events in OW. There is also a Travel Distance, which is the distance to centre line of the projected shadow on the Earth's surface.
Hristo.
On Sunday, December 24, 2023 at 05:47:12 AM GMT+11, V Sempronio <vastronomy@...> wrote:
While planning for events, it is useful to know the distance from the center line for my home location. This helps with calculating exposure/duration limits.
My home observing location is displayed only if I add the event to? "My Events".?
I would like to see the Station Sort dialog show my current "home" location whether or not I have signed up for the event or not.?
the home location info would only be seen on my instance of OW, unless I was signed up for the event.
Vince
|
Feature enhancements to Station Sorts
While planning for events, it is useful to know the distance from the center line for my home location. This helps with calculating exposure/duration limits.
My home observing location is displayed only if I add the event to? "My Events".?
I would like to see the Station Sort dialog show my current "home" location whether or not I have signed up for the event or not.?
the home location info would only be seen on my instance of OW, unless I was signed up for the event.
Vince
|
Re: Magnitude drop error in OW (desktop)
Hi Vince,
Sometimes magnitudes are wrong from the catalogues, sometimes there are close by stars that affect the mag drop calculation, sometimes the stars are very red or very blue and magnirude drops in V, R and B will be all very different, many asteroids have magnitude rotational variations that could make the mag drop vary quite a bit depending on whether the asteroid is at peak or at the dip.
So unless you are using photometric filter while recording and phohometirc magnituides (many are not) when you are calculating the drops, and you know exactly what is the magnitude of the asteroid considering the rotational variations, and you know the colour or the asteroid (most don't have this accurately determined), don't be too concerned about the magnitude drops more than whether it will be a full drop, very small drop or a partial drop.
Hristo.
On Thursday, December 21, 2023 at 12:45:28 PM GMT+11, V Sempronio <vastronomy@...> wrote:
OW is showing, in the list, a 11.6 mag drop for the?(2570) Porphyro of G112411.8+014526 event on 21 Dec (tonight, my time) The details at the bottom of the screen shows a more correct 5.2. The value in the list and the details at the bottom never match, but they are never that far off. I think I found the discrepancy. When I look at the details for the even by right clicking on the even in the list and selecting "Additional Event Details", the following is displayed in the "Event" tab.
Magn Drop (mag) 5.21
Magn Drop (R) 11.6
Begs the question, which is used where, and why? Vince
|
Tim Haymes
V Sempronio
Suhas Gurjar
Carlos Perelló
Claudio Costa