1. Forums
2. Help
3. Why is it that the result of the parameter adjustment is always exactly the same?

Why is it that the result of the parameter adjustment is always exactly the same?

Author: Neop, Created: 2020-07-12 10:11:42, Updated: 2020-07-12 10:17:16

---

---

• FTX used aggregates
• Please teach God the Great to give a limited price stop-loss Python code
• Do a local retest with backtest_python
• Almighty inventor, please add the SCALE function of Civilization, quick die!
• The following error:Buy ((5330, 1): Not select symbol p000
• Please show me how to improve the speed of Python policy retrieval.
• Error: {"Code":3, "Result":"task not found"} What is this error that comes up when tuning the retest?
• How to get the 30-day averages
• Inventors, which digital currency exchanges can cover these digital currencies?
• Is it possible to write a hanging list function in Ma?
• We'll talk about the balance strategy of the Biemex exchange!
• GetAccount: 410: Gone
• The K-line is 1 hour, the lower K-line cycle is 15 minutes, but why is it lost?
• A small suggestion
• How do you write code for the latest market price above the midline of the Blink?
• Why is it that reading tokens today is always wrong?
• What is the Sharp Ratio of all the sharks in the building?
• When multiple exchanges operate normally the first time, exchanges[0] operate normally the second time, exchanges[1] have an error, output content is empty.
• How does the Python language judge dif and dea on the 0 axis for the first golden fork?
• In this example, the real-world market has always been like this, tokenized futures.

---

The grassIs the parameter invalid, don't re-assign it in the policy code, it will overwrite

NeopThank you! After removing the assignment from the policy, fine.