The Crushing & Grinding Of Gypsum ? Introduction

Society for Mining, Metallurgy & Exploration
E. J. Hammer
Organization:
Society for Mining, Metallurgy & Exploration
Pages:
8
File Size:
389 KB
Publication Date:
Jan 1, 1969

Abstract

In the crushing and grinding of metallics for beneficiation, the sizing is normally done to liberate the metals or sulphides for further processing to improve recoveries of the basic metals or minerals. The objective is to reduce the ore in size through various closely controlled stages to that degree of fineness which gives an economic liberation of valuable mineral, but which avoids as much as possible the production of sliming fractions. A different philosophy applies to the crushing and grinding of Gypsum. Our requirements normally demand controlled grinding and/or crushing of the material not only to a fineness suitable for further processing of the mineral into end products, but to produce various sizes of material which are them- selves saleable products. The majority of our tonnage ultimately ends up in stucco for Wallboard. Therefore, our mineral reduction is normally designed toward this end, but it is done in a manner that permits drawing off inter- mediate products to meet various Customer requirements. This forces us into compromises at times in our equipment installations, and our equipment must sometimes be more versatile and complex than we would like it to be. We try to process our basic rock, Gypsum, for the most efficient size reduction. We market 5 to 6 different sizes intermediate to the end product, which generally is the fineness of material to be used for stucco for Wallboard, and we do this with controlled crushing, grinding and sizing cycles of the material. To summarize, we use a different philosophy of crushing and grinding than the metallic field which uses comminution or crushing and grinding to improve recovery, whereas we choose our equipment to crush and grind primarily for product performance.
Citation

APA: E. J. Hammer  (1969)  The Crushing & Grinding Of Gypsum ? Introduction

MLA: E. J. Hammer The Crushing & Grinding Of Gypsum ? Introduction. Society for Mining, Metallurgy & Exploration, 1969.

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 :