You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if the check triggers you return a 0 probability. However I think it might make sense to just reset the learnt knowledge as it is clearly outdated to successAmount = 0 and failAmount = capacity and compute the probability from there and relearn knowledge by potentially attempting a payment (depending on the result of the probability result). Of course instead of resetting both variables one could only reset the one variable for which the information is older.
btw I didn't say that before but I like the naming failAmount and successAmount better than eclairs naming high and low or my own naming maxLiquidity and minLiquidity.
The text was updated successfully, but these errors were encountered:
// Mission control may have some outdated values, we correct them here.
It won't fail forever however, after a certain time, the failAmount and successAmount should recover back to their default values of successAmount=0 and failAmount=capacity via the exponential decays. And thanks for having a look!
oh yeah I know that the exponential decay fixes this (: It is also only a minor observation. I just thought in that case one could directly forget the outdated information.
The reason I wanted to emphasize this is in the wider context of weather an exponential decay is necessary at all. (we don't know how strong the decay should be) thus my initial (but not necessarily better) approach would be to continue learning and once we get a contradiction forget everything for that channel and start over with no knowledge. Following that philosophy I thought I pointed out that one could directly forget the knowledge while maintaining the decay that you have.
While doing the information theoretic payment delivery you keep track of two values for each channel in each direction
failAmount
is the amount that in your last observation the channel was not able to forwardsuccessAmount
is the amount that in your last observation the channel was able to forwardIn the follwoing line you make a sanity check:
lnd/routing/probability_bimodal.go
Line 511 in 51df3e5
if the check triggers you return a
0
probability. However I think it might make sense to just reset the learnt knowledge as it is clearly outdated tosuccessAmount = 0
andfailAmount = capacity
and compute the probability from there and relearn knowledge by potentially attempting a payment (depending on the result of the probability result). Of course instead of resetting both variables one could only reset the one variable for which the information is older.btw I didn't say that before but I like the naming
failAmount
andsuccessAmount
better than eclairs naminghigh
andlow
or my own namingmaxLiquidity
andminLiquidity
.The text was updated successfully, but these errors were encountered: