regarding points that form the arrow shape, if they turn out outside the ±180 longitude range - I just "clip" them by adding/removing 180

and regarding the very ship coordinates and today's subtask - well no ships so far swim exactly at the poles, so I'm just not getting edge cases with latitude

previous problematic situation, markers closer to the poles were increased in size, just like anything else in mercator projection

uniform size achieved :) by multiplying the circle radius, used in the arrow shape construction, by cosine of the latitude

upd ship heading markers have been successfully fixed to counter projection's distortion (⁠ ⁠ꈍ⁠ᴗ⁠ꈍ⁠)

with this today I'm concluding a merge in the maritime project with all about markers :D

#buildinpublic #frontend #dev #maps #mapsky #gis #geospatial

(guessing before watching) for integration testing! I remember instantiating these and using them to yank controller actions, to test response contents and time taken

wowowow thats an impressive thing u are making here, I will track it

satisfying basic little jiggle physics from blender

i love making materials that look like hard stuff (like glass) and setting them onto a soft body :DDD also had fun toggling with light source here

#3d #b3d #3danimation #blender #3dart

maritime project heading markers progress: I made them size appropriately, match the size of dot markers

it works, mostly, but closer to the poles arrows become s t r e t c h y - due to the projection influence, which I shall soon neutralize...

#buildinpublic #dev #frontend #webgl #gis #maps #ais

a little reference drawing I actively used for the maritime project's heading marker. WebGL does not understand "arrows" or "triangles" so I had to construct the shape and find the vertices with some mathematics =)

#doodle #mathsky #dev

yeeey this gifted me with a portion of motivation to fiddle with blender

I finally made HEADING (=course) markers in the maritime project!!! 🎉🎉 they're bringing me so much joy🥺

each of them is a GeoJSON polygon, while dots are ships unmoving rn

next tasks are to make them adapt to zoom, and preferably give outline

#buildinpublic #dev #frontend #webgl #gis #maps #ais

that's the rare attitude nowadays I like it keep this up fren

encountered problem with java compiler settings. at this point I already set JDK 21 for the project, module and in maven pom.xml - and successfully coded using the new apis. but during build attempt there were errors exclusively due to the new methods from jdk21 not being recognized (last pic in this post). then I learnt that in this case one should check language level in compiler settings and set it to the respective value (21 in my case). but it wasn't possible here((0(

java compiler settings after updating intellij to 2025 version. where I successfully set language level to the necessary value of 21.

error situation that was happening at build attempts before the fix. specifically the methods made available by the new jdk were unable to be found. despite that in code they were recognized, intellisense included them...

if you struggle to update jdk version in a java project, in particular when working with intellij - the last resort of the previous value can be language level! which in turn can be limited by the ide version! D:

(today had to upd v2022 to v2025 for jdk 21)

#java #jdk #dev #intellij #compiler

y...yes, I cannot show it now, since this selection of accounts has already updated but you can believe me

i had no idea it was not man-made! :0

as the first in the row of "accounts you might find interesting" on the main page here - and you indeed seem such

why not many posts nowadays - because I'm busy with machine learning related tasks, including annotating pics in CVAT...

honestly I don't like ML/AI/data science/data analytics/ ecosystem, due to their non-deterministic nature and python's dynamic typing ﾉ⁠(⁠°⁠ ⁠-⁠°⁠ﾉ⁠)

#ml #machinelearning #cvat

signs for me everywhere to learn about both things 🐋

noted ✍️✍️✍️ meanwhile these days im exploring adding health checks to APIs, I guess will try using them in the context of docker too

the moment in the logs of one of CVAT containers, where there was the same connection error repeating, already something not about wrong credentials, untill I created the cvat database myself manually

the moment in the logs of one of CVAT containers, where there was a total wait for a confusingly long amount of time, untill I realized I forgot to run that my own redis container and finally ran it

CVAT database in my local PostgreSQL, with all the whatever migrations applied successfuly

the redis container in question compared to the rest occupied in CVAT. thats the same container used in my maritime project btw

(2/2)

having fixed the file, I however still got postgres connection error

turns out it was knocking on a nonexistent DB which I had to create

later it just stopped - turns out, waited for redis whose container i had to run

only then I got my CVAT

#docker #devops #containers #database #software

main changes in the main docker-compose file of CVAT: deleted configurations of postgres (cvat_db) and redis containers; environment variables for connection to postgres went to the main anchor (where variables are gathered to avoid repeating) and on this level CVAT_ was added to them. apparently, as I made the conclusion from logs - to override the default connection config, which was adjusted for server and DB created by the postgres instance from the container, that I deleted

more changes for the CVAT docker compose file, that's its end. of course removed the volumes related to unnecessary containers too, and this extra_hosts section I added to all the rest of containers, just in case

successfully logged in and started using CVAT, though so far i dunno what to do with it next but thats another story :D more details on how I was setting this up - in the post right below

today I had to use CVAT (data segmentation program) which is launched with docker compose

the docker compose included postgresql and redis

which I both already have

so I removed their config from the file and connected the rest outwards

(1/2)

#devops #docker #compose #containers #software

aww thank you thank you, i agree, its a grand as heck thing to be making and i love it (⁠ﾉ⁠≧⁠∇⁠≦⁠)⁠ﾉ⁠ ⁠ﾐ⁠ ⁠┻⁠━⁠┻ it's not completed yet by the way, will be m o a r features, u are welcome to subscribe

and I found my usb on a sink in a random bathroom at one of my rare visits to mom's job, which was completely unrelated to programming. and by rare I mean I used to come there just a few times a year

i mean... I wanted to say you're first someone else I heard about who got their programming learning materials out of the garbage 😅😅😅 I found my fateful usb with a c# manual in a... very unexpected place similarly

my story with c# started very similarly :DD except for I successfully picked it up... and there began what I am now

frens I'm back and with news: I won't need lua

I planned to add scripts to redis db of the maritime project, to merge data.. but reorganizing hash tables was enough (last post) + with my amounts of data the single-threaded lua in redis would block db for noticeable time

#buildinpublic #redis #lua

in my opinion, the biggest advantage of this refactor is readability, but yes - the frontend part has become really straightforward, i can say peaceful :) it just transforms the obtained arrays with ship marker data into geojson points that go onto map. not storing this stuff anywhere in js

thank you for motivation :< 👉👈

prior content of the hash table with ships' coordinates. these were objects with latitude and longitude properties, encoded into bytes (with messagepack...) and stored under MMSI (=real world id) of a respective ship. hash table with type ids was more readable, because those are simple values, but still, it was separately...

content of the single hashtable with all ships' data now. organization of such compound keys under one table instead of making many hash tables per each ship (which is way more popularly advised working with redis) was chosen to be able to conveniently retrieve aaaall data to make checkpoints, in one simple HGET command

main part of the hosted service that accepts AIS data from gRPC connection. both coordinates and ship type data are saved in the same redis hash table under compound keys, like in the previous pic

main part of the hosted service that sends ships' checkpoints to frontend. all the entries are retrieved in one command, as it is said in the post. then checkpoint instances are constructed from entries (they are absolutely not guaranteed to come in order). the "mmsiShipMap" is a concurrent dictionary where keys are MMSIs as string (because they are cut out from hash entry names, which are strings), and values are the checkpoint instances. property values are applied to them along with finding hash entries with the same mmsi in the big collection received... and the results are sent by signalR in one action. prior to this, almost identically working merge by mmsi was on CLIENT side, ow ow ow, and caused "out of memory" errors from time to time 🥴

i'm back to the maritime project! refactored redis storage of arriving #AIS!

❌ Before: 2 hash tables for ship types and coords, latter are stored as bytes, joining data on frontend

✅ now: 1 hash table with clean fields, all marker props in 1 class

#buildinpublic #dev #redis #dotnet #aspnet #gis

have some file path shenanigans from windows which I bumped into when working with files in java

didn't think about getting a path referring to current folder by entering a dot . 😅

and in the last pic, I guess it was trying to find a folder name in input with the /

#java #dev #filesystem #til

initial problematic situation - I joined an edge loop into a face, and got this weird warp, initially I suspected that the problem was with normals

...so I flipped the normal of this face. I must say it helped, but partially - the weird warp decreased but didnt go away still

what resolved the problem: in Layout mode go to Geometry data (afaik you can just click on the green symbol near the mesn name) and Clean Custom Normal Data. I guess this helped because the model was imported from fbx...

problem fixed, no warp, no custom normal data either :D

found a random blender tip when patching a model (from time to time I try 3d :))

a face looked warped despite very simple geometry, I tried flipping normals (helped but partly), mark/clean sharp, more bevel, toggling autosmooth..

right answer was to Clean Custom Normal Data

#blender #3d #b3d #til

y'all won't believe who suddenly has to learn LUA

one of the most random and unexpected things professionally nowadays, but turned out I need some for the maritime project

(try to guess in the comments why :> 👇)

#ScreenshotSaturday #lua #dev