Tactics Plugin

[juancho38]

Originally Posted by rgleason

So what would be the best way to do this? Hoover over the layline and have a yellow popup message as ocpn_draw does sometimes?

Quite frankly I haven't thought about it much, nor has Petri (I think).

I don't really know, something simple. I was thinking about a yellow popup as it appears when you mousse point a route segment ... with just course indication (two values = heading and distance)

Could be nice ...

PS; We may talk about the same thing. I don't understand what you mean by "hoover" ... for me hoover is a vacuum cleaner !

[bcn]

Originally Posted by juancho38

PS; We may talk about the same thing. I don't understand what you mean by "hoover" ... for me hoover is a vacuum cleaner !

"Hover" - estar en suspensión o flotar encima.
Do you remember the "Hover-crafts"?
"Mouse-over" in this context.

[juancho38]

Originally Posted by bcn

"Hover" - estar en suspensión o flotar encima.
Do you remember the "Hover-crafts"?
"Mouse-over" in this context.

We do speak about the same thing then !
Cheers.

[rgleason]

"Hover" - estar en suspensión o flotar encima.
Do you remember the "Hover-crafts"?
"Mouse-over" in this context.

Gracias por corregir mi typo error.

[juancho38]

Que tal la idea entonces !? :-)

[Canne]

I would suggest that if the good idea did not get sucked in the Hoover, one would convert it as a Feature request in Tactics - looks like Thomas is annoying himself, having not enough work !

Knowing the lines are rendered OpenGL, maybe we could get inspired from an excellent WebGL application you all know, windy.com: it renders the pressure values in lines like this:



And they move along the lines magically!

[rgleason]

Yes, Juancho
Perhaps you can register on Tracker

and add this feature request to pi_tactics?

[juancho38]

Originally Posted by rgleason

Yes, Juancho
Perhaps you can register on Tracker

and add this feature request to pi_tactics?

Thanks for your invitation.
I'd rather leave you guys with opencpn experience manage the roadmap.
This is just an idea...

Cheers.

[rgleason]

Juancho, the tracker is simply a list of reasonable feature requests. Users vote for them and you should too. Eventually one of the feature requests gets enough votes so it gets put on the "vetted" features list. That is for opencpn.


For plugins it is simpler. It gets put on the list and voted for. The developer decides if they want to implement or perhaps someone else.


You should join and add the idea and vote.


In thinking about this idea. The time I want to know the exact layline, is when I am about to tack, in order to make the mark or not overstand it.


The information we need is the direction to the mark and the layline to the mark. This is probably better presented as an instrumnt so you can see the numbers, rather than inserting it in the graphic, because the graphic really has visually what you need to know. BTW the layline does not factor in current and leeway etc.so it still requires judgement.

[Canne]

Originally Posted by rgleason

...
The information we need is the direction to the mark and the layline to the mark. This is probably better presented as an instrument so you can see the numbers, rather than inserting it in the graphic, because the graphic really has visually what you need to know...

Juancho, Rick makes a good point here: as a solo sailor I have no time to watch these jumping lines and even less if they have tiny numbers on them! I rather drive the optimal VMG angle data calculated by Tactics on my NKE tl25 mast display (section 3.7 in Tactics manual).

If no such a display which understands the Tactics generated $PNKEP sentences is available, you can show on the screen the optimal CMG angle and your performance against it. First, you see that you are doing like this:

You'd improve and get to this performance and can be pretty happy!

(the boat has moved, meanwhile, towards the waypoint - hence the target speed change, look only at the percentage!)

Please see for the details the attached test report of the similar use case like yours.
TCR4029_2019-07-29.pdf
It is simulated so the lines are not jumping and do not need to be smoothed. No need to read all of it, jump on page 5, check images of test steps 5 and 6. You will see that in optimal and ideal world, when the imaginary boat is doing 100 % polar performance (see polar compass) towards the Tactics Waypoint, both laylines are also aligned with the true heading. Here's a visual signal... but I am afraid that in real life situations that will never happen, or it will not be visible long enough.

Best regards,
Petri

[rgleason]

Those are good points Petri.

The other idea that might help is that as you sail on one tack, the further away you are from the mark, and as you approach the layline for the mark, the CMG, no sorry, I mean VMG (to mark) will start to drop and eventually go to 0. When it hits zero is exactly when you have crossed the layline and should consider tacking to the mark, dependent on tide and wind oscillation.

I suppose you could make an instrument that counted the yards to the layline.

[juancho38]

I understand, there are plenty of ways to follow the indication.
My idea was just to have a simple display of what is drawn ...
@Canne: interesting your pdf file.

Cheers,
JM.

[rgleason]

Juancho, it is definitely worthwhile thinking about the alternatives and then proposing something explicit enough in tracker so it can be executed by a programmer without time spent thinking "how" best to do it.

[Schnapsy]

dashboard_tactics_pi v0.4.1

Hello,

I wanted to change some elements of the dashboard.
For color and appearance, no problems.

On the other hand, to change the number of digits to the display of the pressure of the barometer (2 digits instead of 3) and the indication hPa rather than mBar, I could not compress dashboard.pi into a DLL, so i worked with dashboard_tactics.pi.

So I got a new DLL and everything seems to work well.
But...

But comparing the "official" dashboard with the dashboard_tactics, I see a difference in the display of the apparent angle and wind speed screen.

On the dashboard_tactics, the wind angle never indicates starboard, only port.
(see illustration, but this is not the case for displaying the apparent and true wind angle).

Two questions :

1 - which sentences / lines should I modify in dasboard_tactics.cpp to correct this error ?

2 - what are the files that I miss to compress directly dashboard.pi in a DLL (which will avoid me to install dashboard_tactics.pi which I do not really have utility given my heavy boat ...)

[Canne]

Hi Schnapsy, sorry for the late reply, I just saw your message. In reverse order:

#2 How to use ov50 Dashboard_pi v1.2 code only and drop Tactics:

In CMakeLists.txt turn off Tactics code and modules, in line 27:

SET(TACTICS_INSTRUMENTS OFF)

I just tried and and it compiles and builds and even run otherwise nicely but there is one typo in an #ifdef you need to fix like this. Remove or put in a safe place the DashT build, make a new build-dir and run cmake again in it.

If you've been running or just trying Tactics instruments, I recommend to remove all the instrument panels from you *.ini file, the old Dashboard does not know about the new Tactics instruments which may be lurking around in your *.ini file. Start from scratch with those.

This would resolve your issue, I guess.

#1 Bug fix - it was indeed a bug, thank you, now fixed with this patch - test report:
test_run_TCR409_use_case_TC48_test_plan_TP5_2019-08-19.pdf
in case you will continue with DashT: I'll put that in v0.4.2 end of this month.