hecturchi
Joined 9 years ago
Joined 9 years ago
It is not more secure per se, replacement is done as part of LZB being phased out Europe-wide.
They could have waited for recovery etc. The issue is they switched to manual and then botched it. We don't know root cause yet (bad management, timetable pressure, lax work culture...?).
Same mistake was made with other train and the driver replied that that was not allowed, and the operator corrected accordingly. But the driver of the train that crashed didn't raise the issue.
As it looks now the controller made a mistake when taking over manual control of the segment after systems failure ("continue as normal" vs "continue slow"). The train driver probably should have also known they should not drive at normal speed without safeties in the segment, but I guess they trusted control had cleared previous trains.
Between 10-20 minutes control room did not realize a train was approaching an occupied section where the other train was holding on a red track signal.
Human error but signals serious deficiencies at protocol, oversight etc. In control room.
My experience is that draft-mtp=2 gives 25% improvement in tokens/s but the model is unable to call tools with the right arguments reliably. I have since then gone for smaller quants at draft-mtp=1 and that problem is at least gone so far.
An agent needs to repeat tool calls in the right way, so cannot penalize repetition. This however leads to the agent retrying the wrong calls constantly.
- Hard to benefit from thinking and preserve thinking given token cost.
- Low quants reduce accuracy heavMTP draft can make it make the same mistakes all the time when calling tools, formatting output or following basic guidelines. Otherwise 2x-4x slower.
- K/V quants probably quantized too make things less accurate.
Useful would be combinations with:
- Full context size so it can code and think a bit.
- Draft MTP <= 2 so it doesn't trip
- Q4 quants or better so its accurate
- q8 cache or better so it stays accurate.
- 20 token/s so it finishes while reviewing previous step.
- 1000 tokens/s context load so compactions don't waste 10+ minutes.
- And enough left RAM for 50+ context checkpoints so that it can progress quuckly.
Closest you have is Qwen3.6-35B-A3B-MTP.
Latest gens (Qwen3.8 and co.) are just too big for low specs. 27B dense models seem to be ok for integrated >=92 GiB RAM.
Source: I have low specs and tried them all for agentic use + coding.
I'm still clarifying the purpose of this before making a complaint to the data authority.
Old issue, affects also web UI not only bridge:
https://web.archive.org/web/20240221213617/https://github.co...
Would you use a secure email service that breaks signature verification on received emails? There were a lot of smaller and bigger things along the years, but realizing I could not verify authenticity of signed emails for apparently no reason pushed me over threshold to leave them.