2. Can IVF 11.1 work well with Array Visualizer without visual studio standard/pro. edition (just installig the "shell" edition)? And is there an easier way to have them worked togother?
I'll check out the broken link - it worked just a few weeks ago, I know.
I have tested this with 11.1 and it works. I don't know of a reason that it should not work with VS2008 Shell. You will need to run the attached "repair" program after installing Array Visualizer the first time to get it hooked up with Visual Studio - after that it should work automatically.
Thank you for your reply. The download link was repaired, and I got the Array Visualizer.
Would you please upload the "repair" program ? Thanks a lot.
HC
Hi Steve,
I've downloaded the repair program from the following post: http://software.intel.com/en-us/forums/intel-array-visualizer/topic/57537/
IVF11.1 is now working with AV 3.3!
However, I can not get the "color map" and "label axis" to show up in the debugging environment. My question is similar to the following post: http://software.intel.com/file/507 http://software.intel.com/en-us/forums/intel-array-visualizer/topic/55983/
And "marker" can not show up in the "HeightPlot".....
Could you please indicate how to solve these problems? Or... is it possible to integrate the previous versions (e.g. v1.6) of Array Visualizer with IVF 11.1 ?
I am not an expert on the use of Array Visualizer. You can ask in our Array Visualizer forum. No, it is not possible to integrate the Compaq version of Array Visualizer with Intel Fortran.
I have been unable to use the array visualizer on Win 64XP with VS2005. (I can use it on Win32). On Win64, the "viewarray" remains greyed-out. I can use it on Win32.
I had posted this problem on the Array viewer forum but got no response.
Yes, I ran the repair program. Unfornately, it still does not work.
Here is what I have:
(1) Win 64XP with VS2005 professional (2) Array visualizer installed from av_dev_em64t.zip (3) It gets installed in "C:\Program Files\Intel\Array Visualizer" and not Program Files (x86) (4) I added "C:\Program Files\Intel\Array Visualizer\lib" in Tools->Options->Intel(R) Visual Fortran->Compilers->Libraries (5) I added "C:\Program Files\Intel\Array Visualizer\include" in Tools->Options->Intel(R) Visual Fortran->Compilers->Includes. (6) For (4) and (5), the compiler selection: is Platform == Win32 and version 11.1.035 [IA-32] (7) I closed VS and ran the repair program.
When I run a test project in debug mode, "view array" remains greyed out both in dropdown menu and right-click when an array is selected.
I would guess that you want to install the IA-32 AV if you want to view arrays in 32-bit applications.
Steve
I uninstalled em64t and installed ia32. This time the default install directory is in Program Files (x86). Still no success though. I followed all the steps as exactly as before with new paths.
Also the download site gives the installers based on operating system and hence I had installed the em64t version before.
AV is a good tool and I miss it. But so far I have not found a way to make it work on Win XP64 with VS2005.
I have no expertise on the subject to share with Abhi, I'm afraid, but thanks to this thread I've just got Array Visualizer working on my system (IVF11.0 in VS2005 on 32-bit Vista) and it blows me away: I had no idea that this package was available, and I shudder to think how many dozens, if not hundreds, of hours I might already have saved if I had known about it (I do a lot of image processing, and using the standard VS debugger if you want to find an error in a large 2D matrix you are reduced to dumping megabytes of data onto disk to be combed through offline, or adding debug code to produce various 1D cross-sections through where you think the problem is).
Strangely, from reading the documentation, it seems that once this product was a standard part of first Compaq and then Intel Fortran, and available for purchase separately, but since 2006 or so (just before I started using IVF) it became a free, unsupported download and (at least from me) a well-kept secret. I'm baffled why that should be, but very grateful that you've now pointed me towards it.
The short story is that Array Visualizer was the work of a wonderful engineer, John Readey, who left Intel (his choice). At that time, management decided that it wasn't worth assigning another engineer to. Over the years, I've been trying to get people interested in AV and have found an engineering group willing to take it on, but management still doesn't think it's worth the resources, so the effort is stalled.
Array Visualizer was part of Digital/Compaq Visual Fortran Professional Edition, and was completely rewritten and improved as part of Intel Visual Fortran. It was never sold separately (there was a free "array viewer" download which lets you run applications that use AV but not develop new ones.) Note that not only is Array Visualizer integrated with the debugger, but it can be used on its own from Fortran, C++, VB and other languages. It also has support for HDF5.
I'd be happy to hear more from others of what Array Visualizer means to them and how they think it would benefit the product and Intel. Indeed, I've VERY recently been asked to collect such comments, so you've given me a good opening. Reply here or send me mail at steve.lionel at intel.com - it would be more helpful if you include your name and company/organization.
I have tried various combinations (emt64, ia32, and program files, program files x86 etc) but I still can't get it to work. I can confirm this happening with other computers using Win64 XP and VS2005. But since these computers are within the same company, may be there is a problem with configuration.
Is there any way you can reproduce/test if this combintion is the culprit?
I think that since the array visualizer is not "supported", it is becoming more difficult to get resolution to such basic problems and thus may hinder its wider usage. I had posted this problem on Array Viewer forum a looong time back but it just went cold.
The short story is that Array Visualizer was the work of a wonderful engineer, John Readey, who left Intel (his choice). At that time, management decided that it wasn't worth assigning another engineer to. Over the years, I've been trying to get people interested in AV and have found an engineering group willing to take it on, but management still doesn't think it's worth the resources, so the effort is stalled.
Array Visualizer was part of Digital/Compaq Visual Fortran Professional Edition, and was completely rewritten and improved as part of Intel Visual Fortran. It was never sold separately (there was a free "array viewer" download which lets you run applications that use AV but not develop new ones.) Note that not only is Array Visualizer integrated with the debugger, but it can be used on its own from Fortran, C++, VB and other languages. It also has support for HDF5.
I'd be happy to hear more from others of what Array Visualizer means to them and how they think it would benefit the product and Intel. Indeed, I've VERY recently been asked to collect such comments, so you've given me a good opening. Reply here or send me mail at steve.lionel at intel.com - it would be more helpful if you include your name and company/organization.
Hi Steve,
I think the Array Visualizer integrating in the debugging environment is wonderful. It is the reason why we are still using visual fortran.
I just have one suggestion:
Array Visualizer should be straight-forward while debugging. I think the previous versions are more useful in that way. For example, data display, data marker, palette, and the axes are automatically displayed. Users can investigate the specific data/values immediately, and don't have to setup these items every time. http://software.intel.com/file/507
Thanks for your comments. I'm a bit confused, though - your screen capture looks as if it comes from an application and not just the "View Array" in the debugger. Am I mistaken?
Re: Intel64,
I was unable to get this to work - sorry. I will ask someone to look at it, but since this is officially unsupported, I can't make any promises.
Thanks for your comments. I'm a bit confused, though - your screen capture looks as if it comes from an application and not just the "View Array" in the debugger. Am I mistaken?
Re: Intel64,
I was unable to get this to work - sorry. I will ask someone to look at it, but since this is officially unsupported, I can't make any promises.
Hi Steve,
Please refer to the page 184-187 in the following document: http://www.scribd.com/doc/15880681/Compaq-Visual-Fortran-OVERVIEW.
The data marker, color palette, and axes are instantly displayed in the 3D plot while debugging :D
I believe that your Intel64 remark is in reference to Win64 XP problem. Thanks for giving it a try. I remain hopeful that I will get a solution/work-around....
Your management did not know the value of the gem of a tool they had with AV. As a professional software developer and founder of a handful of software companies (tools and utilities), AV was one of the slickest things I've seen or used. True, AV did and does need improvement (has bugs in IVF implementation).
Your management did not know how to understand this tool, nor how to market it.
The best parts of AV
a) The presentation driver/app is in a separate process from the host application (uses memory mapped files). Meaning on x32 platform it requires very little memory in the host application process VM. And meaning, a single threaded host application gains multi-threaded capability by having the presentation performed in a separate process (concurrently) with execution of the application.
b) While host application is running, pumping results into AV, you can interact with the presentation process (AV) and add charts without interfering with the running of the application. This is realy cool.
In the simulation work I do for my space elevator research I typically have an animated 3D plot of the elevator, earth, moon, etc... Run times can be several days. While running a simulation I may be interested in, as an example, following the bobbing of the upper ballast object. My standard presentation plots (animate 3D), has the data to plot this but not as a 2D chart. To add this 2D chart, it takes about 30 seconds and I can do this without interrupting the simulation run. As long as the tables are "watched" that data is available for ad-hoc plots.
True, the tougher charts and plots you will want to hard code into the program. For the easy ones, it is so easy to do you do not bother with writing the code.
Your management did not know the value of the gem of a tool they had with AV. As a professional software developer and founder of a handful of software companies (tools and utilities), AV was one of the slickest things I've seen or used. True, AV did and does need improvement (has bugs in IVF implementation).
Your management did not know how to understand this tool, nor how to market it.
The best parts of AV
a) The presentation driver/app is in a separate process from the host application (uses memory mapped files). Meaning on x32 platform it requires very little memory in the host application process VM. And meaning, a single threaded host application gains multi-threaded capability by having the presentation performed in a separate process (concurrently) with execution of the application.
b) While host application is running, pumping results into AV, you can interact with the presentation process (AV) and add charts without interfering with the running of the application. This is realy cool.
In the simulation work I do for my space elevator research I typically have an animated 3D plot of the elevator, earth, moon, etc... Run times can be several days. While running a simulation I may be interested in, as an example, following the bobbing of the upper ballast object. My standard presentation plots (animate 3D), has the data to plot this but not as a 2D chart. To add this 2D chart, it takes about 30 seconds and I can do this without interrupting the simulation run. As long as the tables are "watched" that data is available for ad-hoc plots.
True, the tougher charts and plots you will want to hard code into the program. For the easy ones, it is so easy to do you do not bother with writing the code.
The short story is that Array Visualizer was the work of a wonderful engineer, John Readey, who left Intel (his choice). At that time, management decided that it wasn't worth assigning another engineer to. Over the years, I've been trying to get people interested in AV and have found an engineering group willing to take it on, but management still doesn't think it's worth the resources, so the effort is stalled.
Array Visualizer was part of Digital/Compaq Visual Fortran Professional Edition, and was completely rewritten and improved as part of Intel Visual Fortran. It was never sold separately (there was a free "array viewer" download which lets you run applications that use AV but not develop new ones.) Note that not only is Array Visualizer integrated with the debugger, but it can be used on its own from Fortran, C++, VB and other languages. It also has support for HDF5.
I'd be happy to hear more from others of what Array Visualizer means to them and how they think it would benefit the product and Intel. Indeed, I've VERY recently been asked to collect such comments, so you've given me a good opening. Reply here or send me mail at steve.lionel at intel.com - it would be more helpful if you include your name and company/organization.
Our company used Array Visualizer for several years since the DVF/CVF versions. We were using it in-house for several projects and were seriously considering it for a commercial version of one of our models. We consider it an excellent product with great potential for many applications. However, since it was announced that Intel was not going to support it anymore, our company decided not to spend more time in it and go with another set of visualization tools.
It is a shame that such wonderful tools are discontinued in this way.
this is a follow up on the previous thread because I still don't see the solution:
1) I use Intel Visual Fortran Compiler v11.1 2) I have installed Array Visualizer v3.3
Currently, on right click of an array I wish to display I cannot select the "View Array" Option. So I guess I have to link the Compiler with the Visualizer. But...
How do I link the Compiler with the Visualizer, i.e., how do I add the path?
No, you don't have to link anything. Try running the repair tool linked here.
Hi Steve, I tried the repair tool. Array viewer is still greyed! Here is what I have: 1). I installed IVF 11.1 (Intel® Visual Fortran for IA-32 and Intel® 64 (with Microsoft Visual Studio 2008 Shell and Libraries*) 2). Array visualizer 3). Added the path of lib, include, and bin directories of AV in Tools->Options->Intel(R) Visula Fortran ->Compilers 4). Ran the repair tool for VS 2008
I tried intalling the AV first, then VS and VF but still I have the same problem.
I ran the repair tool and all DLLs were found. Now, when executing the code I can the "Array View"-Option is activated in the drop down menu. But when I click on it, Visual Studio shuts down with the error message: "Visual Studio has encountered problems and needs to shut down". This is a bit unfortunate. Everything else continues to work. Can you help out?
