Screenshots look amazing!
Would be nice if it can be implemented into Wavelog!

But also keep in mind: such a DX-cluster is also 'DATA-Heavy', it requires a substantial data transfer

Hi Oliver. As PE1PQX says, this looks great! Thank you for supporting us, and it was a pleasure meeting you this summer in person!

We will take a look at the code and perhaps steal some ideas, but unfortunately, even with your code, it won't be possible to transfer it to Wavelog as it is. There are many reasons for this, ranging from the stack used, to compatibility issues.

I guess the filtering is probably the biggest thing, and I know that can be improved. Though I did do an effort into mode derivation, and fixing the DXCC status filter. As you say, it probably supports 95% of the users, while power users (like you), find other ways :)

I appreciate you taking the time doing this, and showing it to us. Perhaps others will join you in improving this to be even better.
We'll link it in the Wiki, so that other users can find it.

Happy DX hunting. Andreas.

Hello Oliver,
I want to add some thoughts about NodeJS in Wavelog. I absolutely agree with @AndreasK79.
NodeJS is the future of dynamic web apps. This is no secret and Wavelog will need to move toward a more modern tech stack. The biggest issue here is that many users run Wavelog on cheap hosters and shared hosting services that only support simple LAMP stacks. If we switched to NodeJS modules right away, we would lose these users, which we don't want.
Therefore, we need to find a way to implement modern technology while keeping legacy systems running. As you may have heard, I'm working on a new contesting module that will be written mostly in JavaScript as well. This will require a JavaScript backend, which brings us exactly to the point where we need to define how to implement modern solutions.
This new module will come with a guide - a guide on how to implement modern technology into Wavelog while preserving legacy modules. This will require us to embrace Docker more and make NodeJS components usable in containers, while PHP-only users can still use their existing setups.
As you can see, it's not that simple and requires not only technical decisions from the Wavelog team, but also strategic ones. This needs time and work - alongside our normal lives. Wavelog has had a rocket-like start in the last 1.5 years, which has been very time-consuming for the whole team. While we try to keep the pace high, this whole "new-tech-topic" needs well-thought-out decisions.
@AndreasK79 linked your Cluster UI in our external tool list, and we'll definitely steal some ideas for the new contesting module. Until then, I want to say thank you for your support and contribution. This is what makes our community stronger. Thank you for being part of this.
Vy 73
HB9HIL

Thank you all for the feedback. I’ve been heads-down on morsetrainerpro.com, so I’ll pick the DX cluster back up next week. Next on the roadmap are alerting features (think HamAlert-style), and I may even build a companion mobile app. I also want clicking a spot to auto-populate the logging fields, plus add integrated rotor control and full radio control—everything in one interface. I’m not trying to replace Wavelog; Wavelog is bloody fantastic. What I’m missing is tighter radio and rotor integration, ideally in a platform-independent way so anyone can use it.

Wavelog is excellent—no other logger beats its statistics and analytics, period. I’m just a power user, an all-kind hunter, DXer, and contester. I need to see everything at a glance: do I need this station? Worked? Confirmed? What about POTA/SOTA/IOTA/BOTA and Buddha-knows-what else? And can I dial the filters down to only what I care about right now? Flexibility is crucial. Maybe I’m a demanding user and some of this won’t help everyone, but I’m convinced that when hams get the right tools, the whole amateur-radio experience gets better.

New cluster is now released with https://github.com/wavelog/wavelog/releases/tag/2.2 . 😄

BR,
Szymon

Sorry for that,

but the new DX Cluster in 2.2 looks like not finished.

What's wrong?

1, Missing language file:

2, Another font family. WaveLog is using Twemoji Country Flags", "Helvetica", "Comic Sans", sans-serif , DX Cluster Consolas', 'SF Mono', 'Monaco', 'Inconsolata', 'Fira Code', 'Droid Sans Mono', 'Source Code Pro', monospace

3, Time sorting - make a few clicks. First two are okay, after 3rd it is unsorted:

4, Too many coluns:

Why I need to have a large table with Band + Frequency, Mode + Submode, Continent + Zone, Spotter Continet + Zone? Width ot colums can not be set?

5, Polling time too long:

Every second can count.... I remember a story from contester 30years ago. His software combine three or four DX cluster together. He got a DX spot quickier than other.

But now we have fast internet connections. I wan't to know about new DX as soon as is possible.

Look at this:

Do You think it is pretty and useful? I don't. What I want?

1, Fast DX cluster. Max.polling time 3 seconds or set.
2, Clear table. Colums which I don't I would like not to see.
3, Filters: remove unwanted bands, remove unwanted modes, spots de continent, DXCC Status. Maybe Required Flags / Additional Flags.

As a result I got few rows of DX spots. Not overhelmed by unnecessary informations. When I found WaveLog it was like a bang - something that I like. There was only one thing which I am not satified. DX cluster. In 2.1 version I made my own band filter (eg. defined WARC as only DIGI because I don't wan"t to see these bands). Better. Now? Great dissapointment.... If You need help with beta-testing, I am ready to help.

Tested on Opera 123.0.5669.47 , browser cache cleared

Rounded corner:

and not rounded corner:

Are there QO-100 spots?

Question: could I make a roll-back to 2.1 without loosing anything? Or should I make a new install?

Wrong coluns (Entity is not 4O0BMN and so):

Finally 1st thing which I like:

Useful mostly on higher bands to know where the scattering point is.

Hi! @OM0AAO !

I'm NOT part of the Wavelog core team, so this is just my personal view — the WL team may (and probably will) have a different opinion.
As one of the co-authors of this new feature, I’m grateful for your honest feedback — it’s always valuable and usually helps to improve things. Please keep in mind that this is an open-source, non-profit project, developed by volunteers literally at night between regular day-to-day work. So the right question is “how can I help?” rather than “what do I want?”

You asked if help is needed and offered to test, which is great. Help is always needed in projects like this — just check out the dev branch and test, test, test... then create objective issue tickets with your findings. 👍🏻

Now, back to your feedback:

1. Missing SK file — The SK file for one of the 3rd-party components was indeed missing. With limited resources, it’s simply impossible to test every possible user case before release. The Slovak translation also seems to be at 0%, please check
   https://translate.wavelog.org/projects/wavelog/ — maybe you can help push that closer to 100%? This is an awesome way to start contributing to OSS projects.
2. New fonts — Yes, the new fonts were introduced intentionally. This is part of a larger initiative related to
   Prevent user_callsign to have Ø in DB #2528. In the long term, the goal is to have a unified site-wide font with a stroked zero working on all platforms.
3. Sorting behavior — First click = ascending, second = descending, third = sorting off.
4. Columns — The visible columns were chosen based on feedback from a broad user base. Different users have different preferences, but this set should fit most - we are colleting initial user reviews. Making columns resizable and configurable is possible, but that requires additional work hours — it’s a matter of priorities.
5. Cluster performance — The cluster is no real-time due the limits of the technology stack here, there will always be some delay - we are pulling cluster spots every minute here. If someone needs true real-time operation with minimal latency, telnet is the way to go.
   If you meant page/spots load time, with the recent release a properly configured instance should load a cluster/band within a few seconds at most (mine usually loads in 300–500 ms).
   Please check the sample config.php file — there are some cache options you can enable, which will improve the performance of your instance.
6. Corners/layout details — You’re right, there’s some inconsistency there; it can be improved.
7. SAT/RPT support — This wasn’t implemented on purpose as a lower priority. If there’s enough user interest, everything’s possible.
8. Wrong columns issue — Yes, that clearly happened, but I couldn’t reproduce it in Opera. Could you share more details on the steps to reproduce it?
9. Missing features from 2.1 — What features or behaviors do you miss from the 2.1 cluster the most?

Basing on initial feedbacks, I’ve pushed a few post-release PRs today. Feel free to check out and test:
#2586 — test results are welcome; nothing makes software better than testers trying to prove it wasn’t tested enough. 😄

Again, thanks for the feedback!

BR,
Szymon

Hi Szymon,

a part of my work in IT is work as a beta-tester. I think that the new DX Cluster should not go produce in version 2.2.

Yesterday I made few more tests... there is unwanted filter reset after CAT disconnect, missing Favourites filters (didn't find that), font sizes,... . Later I have close the DX Cluster and open Holy Cluster in the window. Not the best but... usable.

Based on https://github.com/wavelog/wavelog/wiki/DXCluster the red line DX spot "red - will be gone at next data fetch (within a minute)". Why gone? It is not outdated.

Cluster in 2.1 can be simple and it is easy to read. Clear table, easy sorting, no ifnormations which are not needed. Look for combination DX, Continent, Zone, Flag, Entity. The DX is enough to recognize all. OK, say that not everybody don't know all prefixes - will be DX and Entity enough? I think yes. More informations could be on hover?

WaveLog is famous in the satellite support. How many logging programs are available for QO-100? I know that only Log4OM can do that. All other have problems, e.g. in ADIF export or too long frequency "10489852 kHz". Missing SAT DX Cluster leads in one more window on the PC - with cluster...

P.S. on the evening I post steps to reproduce Wrong columns issue.

Wrong columns issue steps to reproduce: after applying filter (in my case Phone only). I am using split windows in Opera. This feature is blocking Console in the browser so I don't know exact width of each window. DX Cluster windows is around 1000px?

Now I am using Holy cluster:

Main reason is very clear table - only time, flag, DX, frequency, Band, Spotter and Mode. Font is easy to read. On the hover I got a line on globe (not necessary) and distance + azimuth. And it is fast. But... there is no connection to WaveLog. So I don't know if the spot is new one for me, new slot or anything that I am looking for.

Hello OM0AAO!

Thanks for the response.

• CAT behavior – is being fixed and tested right now. It was indeed incorrect and not tested well enough.
• Favorites – were hidden in the code before release. There’s an ongoing discussion about if and in what form this feature will return; it was intentionally disabled before the 2.2 release.
• Red rows – this comes from our current architecture. Your page is rendered using data received from the DXCluster API.
  A longer explanation would be needed, but in short – DXCluster API receives spots from various sources (telnet clusters, POTA/SOTA APIs, etc.), prepares them for display (detecting contests, references, etc.), then passes them to your WL instance, which calculates worked/confirmed statuses for each of the accounts requesting the DX Cluster. Finally, everything is displayed for you in JS.
  This is a long process designed to scale for large WL instances with thousands of users. At various stages, the admin of your WL instance can limit the cache size for spots – red lines simply indicate spots that were replaced in the cache by newer ones, the logic behind is not a scope of this discusion - DX Cluster just display the data.
• SAT spots – as above, your request is understood. We’ll keep monitoring the need and decide if it’s worth investing work hours into this, as it would require changing the entire toolchain described above.
• Column issue – thank you! I reproduced the issue and proposed a fix here: #2586.
  The bug you found was caused by logic hiding unnecessary columns on narrow screens designed especially for users doing, what you - displaying cluster at half of the screen, please notice that some of the columns are hidden there.

I’m happy that you found a solution that works for you – that’s the beauty of free software: everyone is free to experiment and use what works best for them. 👍🏻

Thanks again! If possible, we’d love to use your software testing experience – please check the referenced PR and let us know if some of the issues are solved (and hopefully no new ones introduced)! 😄

Best regards,
Szymon

You are right, I have tried real new DXCC for me:

So the label is not clear. "New slot or new country"

Hello all,

the cluster integration seems to me a nice add to Wavelog and it gives a lot of good information. However, I am facing a small problem because I am not using WaveLogGate due to my main rig, a flex-6600, I am using WaveFlexIntegrator app instead.

I know that WaveLogGate works with flrig at same time but I do not see how to configure flrig properly to work with flex-6600.

So, if some of you know how to configure flrig with flex-6600 will be welcome here, tks a lot.

Best 73.

CT1DRB/OK8RB
David Quental

Last time two more occured... but I don't remember them exactly. Today I made a rollback to version 2.1.2 . Slow, but works.

If I remember 1st thing was setting band filter based on CAT (when CAT reads 10m then 10m filter was applied). Not happy with that... I would like to see bands which I prefer.

2nd was hanging CAT when I turn off the radio. Not sure if Wavelog was polling CAT, but the button remains colored as connected (click doesn't change that).