Roasting and Treatment of Auriferous Flotation Concentrates

The Australasian Institute of Mining and Metallurgy
Organization:
The Australasian Institute of Mining and Metallurgy
Pages:
22
File Size:
322 KB
Publication Date:
Jan 1, 1939

Abstract

Email to a Friend
This paper is intended to continue the subject in the light of recent work, from where it was left at the conclusion of the discussion on the excellent paper by the late Mr. Noel Haszard. The position then obtaining is briefly summarised below:-The points which received general agreement at that time were:-'(1) That the gold occurs, probably in an elemental form, in a state of very fine division in the pyrite.(2) That the aim in roasting of Kalgoorlie flotation concentrates should be to obtain the maximum porosity possible. The gold tellurides were amenable to treatment with either a' solution of high lime and cyanide strength combined with fine grinding, or bybromocyanidation without re-grinding.(3) That a low roasting temperature is essential during the elimination of the first atom of sulphur, if the final calcine is to give a good extraction by cyanidation.(4) Even with the best temperature conditions of roasting then determined, and after a period of cyanidation of the calcines until no further extraction was obtainable, the lowest calcine residues obtainable were equivalent to approximately 1·8 dwts. per long ton, based on an original concentrate of pure pyrite.There was some division of opinion at the time as to whether the temperature of the later stages of roasting was significant, and also as to the reason why the initial roasting temperatures had so marked an effect.
Citation

APA:  (1939)  Roasting and Treatment of Auriferous Flotation Concentrates

MLA: Roasting and Treatment of Auriferous Flotation Concentrates. The Australasian Institute of Mining and Metallurgy, 1939.

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 :