Search found 11 matches
- Mon Mar 04, 2024 2:30 am
- Forum: Bug Reports
- Topic: Eviews crash on pageload
- Replies: 2
- Views: 196
Re: Eviews crash on pageload
Thank you for the quick reply!
- Fri Mar 01, 2024 5:31 am
- Forum: Bug Reports
- Topic: Eviews crash on pageload
- Replies: 2
- Views: 196
Eviews crash on pageload
Eviews crashes/disappears with no error message with these instructions and the attached Access database: wfcreate a 2010 2020 pageload(type=access) Database1.accdb "select TEST from MY_TABLE" @freq U 1 @smpl @all Note that we encounter this problem accessing a SQL database but our IT spec...
- Tue Nov 08, 2022 3:54 am
- Forum: Bug Reports
- Topic: Error on multiple wfsave commands
- Replies: 14
- Views: 100660
Re: Error on multiple wfsave commands
I have the same error (Unable to allocate memory for working array) when doing multiple 'pagesave' in a loop and writing to XLSX. My understanding is that this command is using the new Excel writing engine (Eviews 13 Oct 11 build). The error does not always happen and when it happens it is not alway...
- Tue Oct 18, 2022 7:51 am
- Forum: Bug Reports
- Topic: Bug Graph Eviews 13
- Replies: 5
- Views: 2980
Re: Bug Graph Eviews 13
Unless one sets lineopacity(OFF), exporting a line chart to EPS (with the Proc - Save graph to disk command) produces an empty chart - no lines are visible. This does not seem to be intended behavior. Using Eviews 13 Oct 11 build.
- Tue Oct 18, 2022 7:48 am
- Forum: Bug Reports
- Topic: Error 1025
- Replies: 3
- Views: 2598
Re: Error 1025
I have the same error when trying to export a chart with multiple panels to PDF (Eviews 13 Oct 11 build). No error when there is a single chart.
- Tue Feb 12, 2019 3:19 am
- Forum: Bug Reports
- Topic: Missing titles in merged graphs
- Replies: 1
- Views: 3634
Missing titles in merged graphs
Say we have two graphs, each with a title added with the addtext command. If we merge those two graphs with the merge command, the new graph shows the titles correctly. We then add a title to the merged graph, again with the addtext command. So far all is well. The merged graph shows an overall titl...
- Mon Feb 27, 2017 9:43 am
- Forum: Bug Reports
- Topic: Error in command capture for solveopt
- Replies: 1
- Views: 3875
Error in command capture for solveopt
In Eviews 9.5 June 1 2016, when unchecking the box "Use analytic derivatives" in the solver dialog of the model object, the command capture window records fullmodel.solveopt(j=f) whereas it should be (j=n) for "numeric". Indeed trying to run the command with (j=f) yields an error.
- Mon May 06, 2013 8:45 am
- Forum: Bug Reports
- Topic: New w=? option in solveopt
- Replies: 1
- Views: 3424
New w=? option in solveopt
First, thank you for adding the w="?" option to the solveopt options in Eviews 8 as requested some time ago. Testing the April 5 build, however, the option does not seem to work. Using the following line, both from the command line or from within a program: fullmodel.solve(i=p, o=n, j=a, t...
- Mon Jun 11, 2012 9:53 am
- Forum: Bug Reports
- Topic: Typo in model solve window
- Replies: 1
- Views: 3393
Typo in model solve window
Using the latest update (29 May), when you solve a model for the baseline and an alternative scenario, there is a small typo in the messages window: Model: FULLMODEL Date: 11/06/12 Time: 18:51 Sample: 2014 2030 Solve Options: Dynamic-Deterministic Simulation Forward Solution Solver: Newton Max itera...
- Fri Mar 30, 2012 8:00 am
- Forum: Programming
- Topic: Option for solver in program
- Replies: 3
- Views: 5290
Re: Option for solver in program
Thank you for considering adding this option to the solve command. The reason this would be useful is that some (somewhat unstable) forward-looking models solve well when the algorithm only loops forward and don't solve at all (under any of of solvers) when the alrorithm loops both forward and backw...
- Tue Jan 31, 2012 2:14 am
- Forum: Programming
- Topic: Option for solver in program
- Replies: 3
- Views: 5290
Option for solver in program
I am writing an Eviews program and would like to do the equivalent of “unchecking” the box “Solve model in both directions” using the model_name.solve(options) command or in some other way. There seems to be no option to do so, at least in the documentation, but perhaps the option exists? If it does...