Institute of Metals Division - Creep of Indium, Lead, and Some of Their Alloys with Various Metals

The American Institute of Mining, Metallurgical, and Petroleum Engineers

J. Weertman

Organization:: The American Institute of Mining, Metallurgical, and Petroleum Engineers
Pages:: 12
File Size:: 703 KB
Publication Date:: Jan 1, 1961

Abstract

Email to a Friend

High-temperature creep experiments were carried out on indium, lead, and on binary substitutional alloys of In-Pb, In-Sn, In-TI, In-Cd, In-Hg, Pb-Bi, Pb-Sn, Pb-In, and Pb-Cd. The stress at which the power law creep equution breaks down was found to be much smaller for indium and lead than for metals with larger elastic moduli. The exponent over the stress in the power law creep equation was found to decrease upon alloying from values close to 4.5 to values near 3. THIS paper describes a set of high-temperature creep experiments made on high-purity lead and indium and on lead-rich and indium-rich single-phase binary alloys of various metals. These ex- periments were carried out to check two predictions of some creep equations derived by us"2 from a dislocation creep model due essentially to Mott. This model is shown in Fig. 1. Here dislocation loops are emitted from sources, not shown, situated on different slip planes. As the loops expand they come into each others' stress fields and are stopped. However, at high temperatures, as Mott has pointed out.

Citation

APA: J. Weertman (1961) Institute of Metals Division - Creep of Indium, Lead, and Some of Their Alloys with Various Metals

MLA: J. Weertman Institute of Metals Division - Creep of Indium, Lead, and Some of Their Alloys with Various Metals. The American Institute of Mining, Metallurgical, and Petroleum Engineers, 1961.

Export

CSV

RIS

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 :