• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DPAD - client died on me....

Assimilator1

Elite Member
Yesterday DPAD died on me & Windows through up the 'encountered a problem...' messege.
If I restart DPAD this happens & I get the windows error messege again

Muon1 started: configuring...
Detected 1 logical processors
Hello, [TA]Assimilator1
Loading 'results.dat'... OK (3 results)
Loading .bin file... OK (53 results)
latticelist.txt older than 12 hours, attempt
New simulation
Searching for auto-saved file...
No file present
Making new genome...
Making new genome, TrialType=Random... Done
Interpreting lattice file 'PhaseRotD'...
Cannot parse the following expression...
HRF162.857 0.15 [0,2.60763] [-180¦,+180¦]
[FATAL]

Where those 2 squares are i get to shaded in squares in DPAD.
Wth is going on?😕
I tried deleting results.dat but it had no effect.

Anyone get an idea?
 
I had the same thing happen to me. I downloaded the newest version patch and that seemed to work.
 
There is a new optimization, PhaseRotD, and your text indicates that is where the problem starts.

My client wasn't running the PhaseRotD (didn't have the lattice file in the lattice folder), but as soon as I updated it and it loaded, Muon1 crashed hard.

so I removed it from the lattice folder. My config.txt tells DPAD not to auto download new lattices, so it won't come back.
 
Thanks Jon 🙂

Is your config always set to not to auto download new lattices? if so don't you miss out on anything?

I wonder if Stephen is aware of this crashing problem?

[edit]
Seems to be working now 🙂 :-



E:\DPAD>muon1 -c

Muon1 started: configuring...
Detected 1 logical processors
Hello, [TA]Assimilator1
Loading 'results.dat'... OK (4 results)
New simulation
Searching for auto-saved file...
No file present
Making new genome...
Making new genome, TrialType=Random... Done
Interpreting lattice file 'ChicaneLinacB'... Done
Beamline consists of 622 units, genome of 668 parameters
Using seed 186196796
Loading bending magnet fields... Done
Adding components to simulation space
Tantalum rod source data loaded.
Building proximity grid 4x1x50 (200 cells)... Done
Done adding components
Determining nearby components...
Normalising beam...
- Starting -
t = 5.15ns (57983/65376 particles) 2.7 Mpts
 
Yes, I do miss out on new optimizations as they are released, but I check the Muon1 website, so it hasn't been an issue.
It's just that some new optimizations are a little buggy when first released (like this one), so early users can have problems.
 
Fair enough ,btw it somehow managed to d/l that lattice file again even though mine's set to '0' 😕

[edit]Turned out that due to a minor alteration i made to the lattice d/l line DPAD didn't recognise it ,& therefore created a new line with d/l enabled:roll:
 
Back
Top