-
Notifications
You must be signed in to change notification settings - Fork 6
Expand file tree
/
Copy pathReadMe_If_Issue_With_Solver.txt
More file actions
65 lines (38 loc) · 2.36 KB
/
ReadMe_If_Issue_With_Solver.txt
File metadata and controls
65 lines (38 loc) · 2.36 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
IMPORTANT UPDATE
The preferred option is to NOT use the solver (i.e. and to select FALSE in the 'Install Solver Addin').
A solution has been found to improve the accuracy of the 'GoalSeek' tool and it yields results as accurate as the solver add-in.
FIX - TO IMPROVE GOALSEEK ACCURACY:
1. Select 'Options' from the 'File' tab
2. Choose 'Formulas'
3. On the top-right hand side, click on 'Enable iterative calculation'
4. Reduce the 'Maximum Change' figure to the desired accuracy (i.e 0.0000000000001)
Excel Solver might be the cause of a few issues:
1. Solver Installation
If the Solver Add-in doesn't get installed automatically in Excel, please add it manually before clicking on the calibration buttons.
To install it:
Windows
a. Click the File tab, click Options, and then click the Add-ins category.
b. In the Manage box, click Excel Add-ins, and then click Go.
c. In the Add-ins available box, select the Solver Add-in check box.
If you don't see this name in the list, click the Browse... button and navigate to the folder containing Solver.xlam.
Then click OK.
d. Now on the Data tab, in the Analysis group, you should see the Solver command.
Mac
a. Click the Tools menu, then click the Add-ins command.
b. In the Add-ins available box, select the Solver.xlam check box.
If you don't see this name in the list, click the Select... button and navigate to the folder containing Solver.xlam.
Then click OK.
c. Now on the Tools menu, you should see the Solver command.
2. Not able to Install the Solver
If you are not able to install the solver, you might still get some VBA error where the solver is called.
If that is the case, you might need to comment those lines.
We will aim to provide a fix for this in the next release
3. Solver stopping at every scenario
This is an issue we don't have solution for and which seems to be specific to Mac.
If you do find a solution for this, please contact us.
Normally the parameter 'UserFinish' when set to 'True' should deactivate this.
In the sub 'RootFindingIndividualIRQuote' in the module 'rngCalibration' you can try replacing the line:
SolverSolve UserFinish:=True, ShowRef:="SolverDisplayFunction"
by
Call SolverSolve(True, "SolverDisplayFunction")
If this still doesn't work, you will have to set the parameter 'Install Solver' in the 'Configuration' tab to False, so that it uses GoalSeek instead of the Solver