Institute of Metals Division - Some Properties of Vanadium at Subatmospheric Temperatures (TN)

The American Institute of Mining, Metallurgical, and Petroleum Engineers
J. A. Hren C. M. Wayman
Organization:
The American Institute of Mining, Metallurgical, and Petroleum Engineers
Pages:
2
File Size:
110 KB
Publication Date:
Jan 1, 1961

Abstract

RECENT investigators have noted anomalous behavior in the electrical resistivity of vanadium below room temperature. Rostoker and Yamamoto1 in studying the vanadium-oxygen system hypothesized that the body-centered-tetragonal phase existing from 15 to 34 at. pet O at approximately 800°K was really a low-temperature allotrope of vanadium that was stabilized by oxygen. In measuring the electrical resistance of cold-swaged vanadium rod over a range of temperatures, a small discontinuity was observed at approximately 240°K, supporting their notion of allotropy. However, the magnitude of the observed discontinuity was extremely small. Loomis and Carlson2 in studying the ductile-brittle transition in vanadium also made resistance measurements and reported a discontinuity near 200°K. More recently, White and Woods3 showed that the electrical resistivity from room temperature to approximately 100 °K was not linear and at variance with the Bloch-Griineisen law. Instead of finding a discontinuity, they observed a deviation from linearity below 200°K. In discussing their results they pointed
Citation

APA: J. A. Hren C. M. Wayman  (1961)  Institute of Metals Division - Some Properties of Vanadium at Subatmospheric Temperatures (TN)

MLA: J. A. Hren C. M. Wayman Institute of Metals Division - Some Properties of Vanadium at Subatmospheric Temperatures (TN). The American Institute of Mining, Metallurgical, and Petroleum Engineers, 1961.

Export
Purchase this Article for $25.00

Create a Guest account to purchase this file
- or -
Log in to your existing Guest account

Unexpected error retrieving advertisement for PageView: Home_Index, Key: SidebarTop Name : Microsoft.Data.SqlClient.SqlException Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.) Stack : at Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod(Exception e) at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen() --- End of stack trace from previous location --- at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.InitializeReaderAsync(AsyncEnumerator enumerator, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.MoveNextAsync() at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken) at OneMine.Advertisements.Data.Queries.AdvertisementQueries.GetActiveAdvertisementByNameKeyAsync[T](Guid siteId, String pageViewName, String placementKey, CancellationToken cancellationToken) in D:\a\1\s\Lib\Data\Advertisements\Data\Queries\AdvertisementQueries.cs:line 39 at OneMine.Web.ViewComponents.ZoneTagViewComponent.InvokeAsync(String pageViewName, String placementKey) in D:\a\1\s\Web\ViewComponents\ZoneTagViewComponent.cs:line 84 -- Inner Exception -- Name : System.ComponentModel.Win32Exception Message: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Stack :