What are system and software requirements for NodeXL Pro?
OPERATING SYSTEM: Microsoft Windows ™(XP, Vista, 7, 8, 10)
SOFTWARE: Microsoft Office™ (2007, 2010, 2013, 2016)
64 bit versions of Windows and Office are recommended (32 bit systems cannot use large amounts of RAM).
RAM: More the better! 4GB is enough to handle very small networks, 8GB for medium networks, 16GB or 32GB is recommended for very large networks (100K edges and above).
CPU: Most computers are now fast enough to handle network calculations. That said, faster CPUs are good for improving NodeXL’s performance. However, currently NodeXL is a (mostly) single threaded application that does not make use of multiple cores.
What is the difference between NodeXL Basic and NodeXL Pro?
For a detailed feature overview to compare NodeXL Basic and NodeXL Pro please follow this link.
Can I run NodeXL on a Mac?
Mac users interested in NodeXL may use a Virtual Machine.
We recommend REMOTE virtual machines like those offered by Amazon.
Here is an article about creating a virtual machine in the Amazon Elastic Compute Cloud (EC2):
While it *is* possible to run a local VM on a MacBook, this is not a performant way to run the application (it can be slow!).
Further, a MacBook running Windows plus Office plus NodeXL should have no less than 16GB of RAM.
In contrast, the remote virtual machines may be accessed using the free “Remote Desktop” application from Microsoft (available for all Macs):
Remote VMs place almost zero resource demands on the client machine (the Mac) and do not require special amounts of RAM or features to perform well.
What are the differences between NodeXL Pro Commercial, Academic/Non-Profit and Student user licenses?
On how many machines can I run one license?
The NodeXL Pro License Key file we send to you must be placed on any machine you would like to use to run NodeXL Pro.
Place the NodeXL Pro License Key file anywhere on the target machine’s file system.
When NodeXL Pro opens, it will ask you to locate this License Key file. This will then authorize the use of NodeXL Pro on that machine.
When a machine is authorized for NodeXL Pro all other machines that are running NodeXL Pro are de-authorized. NodeXL Pro will not operate on these machines until one of them is re-authorized.
To re-authorize a machine, copy the ORIGINAL license file (the one attached to the license email) to the target machine. DO NOT use the license file from any other machine.
When a license file is authorized, the copy of the license file is imprinted with machine specific data that prevents it from running on any other machine.
Only the original license file can (re-)authorize a machine.
I ordered a NodeXL Pro license key but I did not receive an email with a license key. What should I do?
The original license key email is often sent within a minute of the order. If you do not receive a license key email promptly please check your “Spam” or “Junk” folders. You should also check to see the email address that you used to pay for your license key. In some cases the email associated with your payment is different from your main email address. If you cannot find the original license key in your emails, please send a short note to email@example.com with the exact email address and the payment transaction ID used when purchasing the license.
I lost my license key. What should I do?
If you cannot find the original license key in your emails, please send a short note to firstname.lastname@example.org with the exact email address you used when purchasing the license.
What are the limits of the Twitter data importers?
The use of NodeXL Pro Twitter data importers requires a twitter account. Before your first data import you need to authorize NodeXL by entering a token number which is automatically sent to you during the authorization process.
Moreover Twitter’s public free API has many limits. NodeXL Basic and Pro are both effected by these limits. Data is available only for 8-9 days. Queries cannot return more than 18,000 tweets.The follower network is further restricted: the rate at which queries about who follows who can be asked is low.
NodeXL Pro does not enable the collection of data beyond these limits. That said, NodeXL can process data from commercial data providers (like Crimson Hexagon or Radian6). While these are expensive options, they may be the only way to get historical data from Twitter.
Commercial services like Radian6 and Crimson Hexagon provide archival data – but not cheaply!
You may be able to get a little bit more data from the public Twitter API by using the SINCE: and UNTIL: operators – example:QUERYTERM since:2016-01-21 until:2016-01-27. Since: and Until: operators scope the time frame of the query.
Twitter controls its API and throttles it based on unknowable parameters. We notice that the more the volume of tweets == less tweets delivered. One alternative is to do day long slices and append them in order to maximize the data available from Twitter.
You may also be interested in th Connected Action Graph Server Importer which enables NodeXL to connect to the “STREAM” API from Twitter (which sometimes delivers larger volumes of data).
What are the limits of the Facebook data importers?
The only major limit of the public free Facebook is time. You can get as much historical data from fan pages and groups as you like, yet the network data download may take quite a while as the download stops and resumes.
Please note that the download of network data from large fan pages can easily max out your system memory if you do not limit the number of reactions, likes and shares when setting up the data importer.
What is a 3rd Party Data Importer?
What are the limits of the Flicker data importer?
How can I Merge Workbooks?
You may also be interested in this: http://graphserverimporter.codeplex.com which enables NodeXL to accumulate data from the Twitter API over time.
- NodeXL uses “Named Ranges” for all of the tables and worksheets. Pasting new data in the first blank row may not extend the named range for edges, or it may break the existing named range.
- Pasting data from multiple Edges worksheets can create duplicate Edges
- Pasting data from multiple Vertices worksheets can create duplicate vertices – which NodeXL does not like : -(