EViews.com

Hello, EViews doesn't provide exception-style error handling, but a program can detect that an error has occurred and react rather than simply stopping. For example: setmaxerrs 2 fetch(d="x:\<path-to-a -database\somedatabase.edb") {%CONCEPTS} !error_occurred = @errorcount > 0 clearerrs set...

Hello,

As I recall, the ability to general SVAR impulse responses via bootstrapping was not added until EViews 14. The menu options in EViews 12 are slightly incorrect as they don't excluded that unavailable feature.

Hello, Sine the x axis is a time axis rather than a data axis, it's the "Obs & Date axis grid lines" setting rather than the "Data scale grid lines" setting that controls the x axis grid lines. Instead of turning off grid lines for the bottom data axis (which isn't applicable...

Hello,

EViews' technique is the former, an iterative search over exogenous values.

Hello,

A fix for this issue will be available in the next EViews patch.

Hello, I believe you're seeing correct behavior. The only difference between the two scenarios is a one unit shock to exogenous variable X1 on date 2019m01. Given that the model is entirely linear, any difference between variable trajectories in the two scenarios will be a function of solely your ex...

Hello,

I'll contribute the following snippet. So long as the very first and last months are fully included within the D5 workfile range, the following expression will generate the number of business days in the current month:

My pleasure. While not exactly the debugging path I followed, this particular type of issue would be revealed via a simple visual scan of the exogenous data for NAs. The model "Proc -> Make Group/Table..." procedure is convenient for quickly generating a group of just the utilized exogenou...

Hello, It turns out this is a run-of-the-mill missing data issue. In model MOD_PNT2, the equation for variable CO2_A_0MB references exogenous variable CPI_12(-1). Unfortunately, that series doesn't contain data (only NAs) after 2023M11, thus there's going to be a problem in 2024M01 as you've experie...

Hello, Given that there are no missing values in the data and that simpler variations of your model solve successfully, my first thought is that the full model includes some type of numerical issue that only the data for that one observation happens to trigger. I would certainly like to examine your...

Hello, The algebra performed by the fliptype procedure doesn't consider special cases when inverting functions, e.g., introducing a potential for division by zero where none existing previously. In general, the procedure will just attempt to "solve for" the leftmost instance of the new end...

Hello, The issue is the expressions used in the @recode statements for AFG_80, AFG_70, and AFG_60. You cannot test whether a value is within a range using an expression such as "X80 <= AFG < X90". Instead, use two conjoined relational expressions, i.e. "X80 <= AFG and AFG < X90",...

Hello, The model solution procedure adjusts the solution sample to ensure that all referenced variable lags/leads exist in the workfile. For example, imagine a quarterly workfile spanning 2000Q1 to 2020Q4. If the specified solution sample covered the full workfile, "2000Q1 2020Q4", but the...

Hello, It's possible that if solution values (or expressions they appear in) are very close to numeric singularities, then the adjustment of add factors combined with the solution rounding and significant digits setting could produce such failures. Here's a small program that demonstrates this effec...

Hello, Would that be error 82? It appears that the sirf add-in contains a bug triggered by generating the IRF for any variable other than the first. EViews 13 stops the add-in at that point, but earlier versions of EViews proceed as if the user had specified the first variable. I don't see an easy w...