Quantcast
Channel: NodeXL: Network Overview, Discovery and Exploration for Excel
Viewing all 4386 articles
Browse latest View live

Updated Wiki: CompleteReleaseHistory

$
0
0

Complete NodeXL Release History

1.0.1.247 (In progress)
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text [IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2017-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>


Updated Wiki: CompleteReleaseHistory

$
0
0

Complete NodeXL Release History

1.0.1.247 (In progress)
  • If you import a Twitter search network and then tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text [IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2017-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

Updated Wiki: CompleteReleaseHistory

$
0
0

Complete NodeXL Release History

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and then tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text [IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

Updated Wiki: CompleteReleaseHistory

$
0
0

Complete NodeXL Release History

1.0.1.247 (2013-08-02)
  • If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
  • When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text [IOException]: Unable to read data from the transport connection: The connection was closed.")

1.0.1.246 (2013-07-19)
  • An importer for a new Graph Server has been added. The Graph Server is currently private.
  • Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".

1.0.1.245 (2013-06-19)
  • This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
  • An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
  • This release is functionally identical to version 1.0.1.244.

1.0.1.244 (2013-06-17, private release)
  • In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
  • Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
  • Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)

1.0.1.243 (2013-05-19, private release)
  • The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.

1.0.1.242 (2013-05-01, private release)
  • The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
  • Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)

1.0.1.241 (2013-04-25, private release)
  • Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.

1.0.1.240 (2013-04-24, private release)
  • If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.

1.0.1.239 (2013-04-08, private release)
  • Same as 1.0.1.238, but with additional edge options.

1.0.1.238 (2013-04-08)
  • Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."

1.0.1.237 (2013-03-25, private release)
  • Same as 1.0.1.236, but with additional edge options.

1.0.1.236 (2013-03-25)
  • There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
  • When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
  • If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
  • For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
Go to Page 2 >>

Source code checked in, #72759

Source code checked in, #72760

$
0
0
Updates the NodeXL source code to version 1.0.1.247.

Released: NodeXL Excel Template, version 1.0.1.247 (Aug 02, 2013)

$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release expands the Twitter search top items that NodeXL calculates. See theComplete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.

Updated Release: NodeXL Excel Template, version 1.0.1.247 (Aug 02, 2013)

$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release expands the Twitter search top items that NodeXL calculates. See the Complete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.

Released: NodeXL Excel Template, version 1.0.1.247 (Aug 02, 2013)

$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release expands the Twitter search network top items that NodeXL calculates. See theComplete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.

Updated Release: NodeXL Excel Template, version 1.0.1.247 (Aug 02, 2013)

$
0
0
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.

Please help support the development of NodeXL with your donation.

What's New

This release expands the Twitter search network top items that NodeXL calculates. See the Complete NodeXL Release History for more information.

Installation Steps

Follow these steps to install and use the template:
  1. Download the Zip file.
  2. Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
  3. Close Excel if it's open.
  4. Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
  5. Delete the unzipped files. They're no longer needed.
  6. Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
  7. Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."

Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.

System Requirements

  1. Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
  2. Office 2007 or 2010.
  3. NodeXL has not been tested yet with Office 2013 or Windows 8.

Release History

Please see the Complete NodeXL Release History.

New Post: Partial network problem in Twitter

$
0
0
I'm just following up. I continue to have this problem, but only on the 64-bit Excel/Window 8 machine. The issue is that machine has the most memory so preferred for working on if at all possible. Is there any update on this issue?

New Post: Dynamic degree

$
0
0
Hi, Peter:

I'm not sure when we'll have a chance to get to it, but I've added your suggestion to our feature request list. Being able to perform operations on just a subset of the graph sounds like a useful feature.

Thanks,
Tony

New Post: Partial network problem in Twitter

$
0
0
No, there is no update.

I'm at a loss to explain how the 64- vs. 32-bitness of either Windows or Excel could affect this behavior. Perhaps that's just a coincidence, and something else on the 64-bit machine is different?

Do you get a partial network every time on the 64-bit machine?

-- Tony

New Post: Partial network problem in Twitter

$
0
0

This is not a solution, but is it possible for you to collect data on the 32 bit system and analyze on the 64 bit system?

Marc

New Post: creating sankey diagrams in nodeXL

$
0
0
Thanks Tony. Not to bug you,But I like NodexXL so much. after all the sankey is nothing but nodes connected to each other with edge weights - conceptually. I understand the hard part is laying it out so it looks nice. But Thanks again.

New Post: Calculating pagerank in NodeXL

$
0
0
Hello

Can anyone advise here? If I have data describing the links between a set of web pages, stored in a text file or (run time) program, can NodeXL be used to determine the pagerank of each of the pages?

I have a set of about 500 pages.

Thanks

Martin O'Shea.

New Post: Calculating pagerank in NodeXL

$
0
0
Yes.

If you can get the data into a format that can be imported into NodeXL, calculating pagerank for each page (within the collected network) is easily calculated.

Try loading the text file into an Excel worksheet. Make sure the data is in separate columns and give the first row meaningful names.

Then, open a NodeXL template from the same Excel session. Navigate to the NodeXL menu and select NodeXL>Data>Import>From Open Workbook.

Image

This will import the data you specify into the proper columns for analysis within NodeXL.
Regards,
-- Marc

New Post: Calculating pagerank in NodeXL

$
0
0
Thanks Marc. This may be useful. Can calculating PR in NodeXL be configured though? I mean can a user set a number of iterations to run the calculations for? Or, can users set a pre-defined criteria to govern the difference in iterations for convergence to work?

New Post: Calculating pagerank in NodeXL

$
0
0
Martin:

PageRank cannot be configured in NodeXL. It uses a maximum of 100 iterations, which is a default value set by the SNAP graph metrics library that NodeXL uses to calculate PageRank and other metrics. (SNAP is from Jure Leskovec's group at Stanford: http://snap.stanford.edu/ ).

-- Tony

New Post: creating sankey diagrams in nodeXL

$
0
0
That wasn't bugging, it was a constructive suggestion. I don't know if or when we will get to it, but I've added your suggestion to our feature request list.

Thanks,
Tony
Viewing all 4386 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>