NickH has quit [Remote host closed the connection]
NickH has joined #river
NickH has quit [Remote host closed the connection]
NickH has joined #river
fitrh has joined #river
geemili has quit [Server closed connection]
geemili has joined #river
fitrh has quit [Ping timeout: 256 seconds]
tinwood has quit [Server closed connection]
tinwood has joined #river
tinwood has quit [Changing host]
tinwood has joined #river
whereswaldon has quit [Server closed connection]
whereswaldon has joined #river
upsala has joined #river
angry_vincent has joined #river
midgard has quit [Server closed connection]
midgard has joined #river
angry_vincent has quit [Remote host closed the connection]
wsx has quit [Server closed connection]
wsx has joined #river
szgy has quit [Server closed connection]
szgy has joined #river
ayushnix has quit [Read error: Connection reset by peer]
upsala has quit [Quit: Client closed]
angry_vincent has joined #river
upsala has joined #river
rodrgz has quit [Server closed connection]
rodrgz has joined #river
<ifreund>
sewn: river 0.3 isn't going to disappear anytime soon, you're welcome to keep using it for as long as you like
<sewn>
I'm not hanging on it for life I would just like to know ahead of time if its reasonable
<ifreund>
as for when river 0.4 will be finished, I don't know. At a guess around a year from now
<ifreund>
though it depends a lot on how much time I have for river
angry_vincent has quit [Remote host closed the connection]
angry_vincent has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
angry_vincent has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
angry_vincent has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
angry_vincent has joined #river
voroskoi has quit [Server closed connection]
voroskoi has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
angry_vincent has joined #river
angry_vincent has quit [Remote host closed the connection]
angry_vincent has joined #river
<leon-p>
kinda hoping the wm protocol implementation lands a bit earlier, although holding back a release makes sense to me so we can experiment and iterate on the protocol for a while
<ifreund>
leon-p: yeah, I think the wm protocol will land in master in like 2-4 months or so though probably won't be near release-ready at that point
<leon-p>
oh neat, right in time to distract me from my bachelors thesis :D
<ifreund>
I don't know yet what all I want to get done before landing the initial version in master though so it's hard to say
<ifreund>
perfect :D
angry_vincent has quit [Read error: Connection reset by peer]
<LarstiQ>
so part of the PR approval process is now checking if another section of the thesis has been written? ;)
aryak has quit [Ping timeout: 245 seconds]
<leon-p>
writing the thing isn't reall the problem. It's finishing the program first and then convincing my supervisor that because it's a physics thesis I'd actually like to do some physics as well instead of just implementing some algorithm from some paper
<leon-p>
I was also probably one of the few people who got hit by the socket server from the 0.11.0 zig std being weird, but I only found out that was the issue after reading the release notes
<leon-p>
i.e. my program had issues getting and holding a connection from another server, but after upgrading to zig 0.12 it works perfectly
<leon-p>
now I "just" have to debug some threading issues :')
<leon-p>
and hope that the paper didn't lie and this really can be done in real-time
<LarstiQ>
do simulations count as physics?
<leon-p>
it's not a simulation
<leon-p>
but yes, they do
<leon-p>
we have entire departments that do nothing but write sumlations. and an entire mandatory course on it
<LarstiQ>
aye, just wondering what kind of physics you'd like to do. I mostly know theoretical physicists, not experimenters
<leon-p>
bu what I do: electron microscopes have cameras in them (timepix3 f.e.). a single electron activates multiple pixles. to use the data you need to cluster those pixel activations into hits. right now we have been doing that afterwards with a slow python script. a meassurement gets about 1 Giga-Hit / second, so we have lots of data (a few TB each month). The idea is to do the clustering step in real-time, to avoid down-time (the python script needs up to ten mi
<leon-p>
nutes to cluster a single meassurement) and reduce storage costs
<leon-p>
however my actual speciality is optics, sensorics and imaging
<leon-p>
what I really want to work on eventually are the ultra-fast TEMs. they have a femto second laser to excite an electron emitter. they allow you such crazy things as taking videos of chemical reactions or even the switching of semiconductor logic gates f.e.
angry_vincent has quit [Ping timeout: 252 seconds]
ayushnix has joined #river
adamcstephens has quit [Server closed connection]
adamcstephens has joined #river
tinwood has quit [Remote host closed the connection]
sespiros has quit [Read error: Connection reset by peer]
sespiros has joined #river
tinwood has joined #river
tinwood has quit [Changing host]
tinwood has joined #river
upsala has joined #river
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]
waleee has quit [Ping timeout: 256 seconds]
angry_vincent has joined #river
upsala has quit [Quit: Client closed]
aryak has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
angry_vincent has joined #river
upsala has joined #river
agz has joined #river
<agz>
ifreund: found this awesome talk of yours, as i'm getting myself familiar with the wayland and zig stuff, you should probably be linking it somewhere in your site https://youtu.be/mwrA5IRGpfU (a gem for someone like me who also interested in similar stuff and starting uni this fall)
maxxv has joined #river
eoli3n has quit [Server closed connection]
eoli3n has joined #river
maxxv has quit [Client Quit]
upsala has quit [Quit: Client closed]
waleee has joined #river
upsala has joined #river
Guest11 has joined #river
Guest11 has quit [Client Quit]
upsala has quit [Quit: Client closed]
angry_vincent has quit [Ping timeout: 265 seconds]
agz has quit [Quit: leaving]
kotto has quit [Ping timeout: 258 seconds]
kotto has joined #river
<leon-p>
"4 years ago" ... I feel old now
sonofevropa has joined #river
<sonofevropa>
dropping in for what's probably a quick question. has river been updated to work with zig 13?
Joseph__ has joined #river
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 265 seconds]
<sonofevropa>
I'm unintelligent, it's in the README. figured maybe that was the compilation issues (getting them from the aur and from manual)
<sonofevropa>
i'll keep investigating, sorry for the unnecessary question
sonofevropa has left #river [#river]
Joseph__ has quit [Quit: Joseph__]
vyivel has quit [Ping timeout: 245 seconds]
vyivel has joined #river
Guest97 has joined #river
<Guest97>
Hello, I am tryinging to build river from source, but it fails with "unable to find dynamic system library 'wlroots'" however, I have wlroots-devel installed
Guest97 has quit [Client Quit]
Guest97 has joined #river
<leon-p>
which version of wlroots do you have installed?
<Guest97>
0.17
<ifreund>
does your distro patch the wlroots 0.17 pkg-config to add a version to the name?
<ifreund>
if so you need to patch rivers build.zig to make it find your distros wlroots
<Guest97>
Seems they do
<Guest97>
Assuming I should change one of the wlroots instances in build.zig? If so which one?
waleee has quit [Ping timeout: 246 seconds]
waleee has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
<Guest97>
I've tried changing each wlroots instance to wlroots-0.17 individually now, but it doesn't seem to work still