|By Marketwired .||
|July 3, 2014 01:12 PM EDT||
ST. JOHN'S, NEWFOUNDLAND AND LABRADOR -- (Marketwired) -- 07/03/14 -- Red Moon Potash Inc. ("the Company" - "Red Moon") (TSX VENTURE: RMK) announces that drilling has commenced on its Captain Cook salt/potash deposit in Western Newfoundland. The summer drill program will consist of two holes, CC #4 located approximately 500 metres north of CC #2 which was drilled in 2013. CC #2 encountered 150 metres (303-453 m) of salt including an upper zone of stringer potash beds at 318 m - 329 m. CC #4 is a northeast stepout testing a seismic anomaly interpreted to be a thickened evaporite section (salt - potash bearing interval).
CC #5 is located approximately 1000 metres east of the discovery hole Captain Cook (CC) #1. This is the first hole to stepout in an easterly direction where the evaporite section thickens down dip. These two stepout holes are intended to add substantial tonnage to the salt deposit and further calibrate potash distribution in the basin. Drill location maps are available at www.redmoonpotash.com.
The holes are being drilled by a continuous coring rig operated by Logan Drilling Limited, an established and experienced driller in this geologic environment. Holes are not expected to exceed 600 meters in depth.
The Captain Cook salt/potash project is located in the Bay St. George Basin of Western Newfoundland near deep water ports and an airport. The Trans Canada highway and high voltage electrical power lines cross the property. The project is delineating an evaporite package of rocks analogous to the potash/salt mines in the Sussex basin of New Brunswick. Red Moon owns a 100% working interest subject to a 3% royalty to its parent company, Vulcan Minerals Inc. (TSX VENTURE: VUL). Vulcan is providing project management services to Red Moon, capitalizing on Vulcan's drilling experience in the region.
The TSX Venture Exchange has not reviewed and does not accept responsibility for the adequacy or accuracy of this release. This release may contain certain forward-looking statements. Actual events or results may differ from the Company's expectations. Certain risk factors beyond the Company's control may affect the actual results achieved. Accordingly, readers are advised not to place undue reliance on forward-looking information. Except by law, the Company undertakes no obligation to publicly update or revise forward-looking information.
Sep. 29, 2016 10:30 PM EDT Reads: 4,020
Sep. 29, 2016 10:15 PM EDT Reads: 2,785
Sep. 29, 2016 10:00 PM EDT Reads: 1,804
Sep. 29, 2016 09:45 PM EDT Reads: 3,126
Sep. 29, 2016 08:45 PM EDT Reads: 2,209
Sep. 29, 2016 08:45 PM EDT Reads: 1,546
Sep. 29, 2016 06:15 PM EDT Reads: 3,685
Sep. 29, 2016 06:00 PM EDT Reads: 1,537
Sep. 29, 2016 05:15 PM EDT Reads: 2,855
Sep. 29, 2016 05:15 PM EDT Reads: 1,583
Sep. 29, 2016 04:45 PM EDT Reads: 3,446
Sep. 29, 2016 04:45 PM EDT Reads: 2,794
Sep. 29, 2016 04:30 PM EDT Reads: 1,343
Sep. 29, 2016 04:30 PM EDT Reads: 1,962
So, you bought into the current machine learning craze and went on to collect millions/billions of records from this promising new data source. Now, what do you do with them? Too often, the abundance of data quickly turns into an abundance of problems. How do you extract that "magic essence" from your data without falling into the common pitfalls? In her session at @ThingsExpo, Natalia Ponomareva, Software Engineer at Google, provided tips on how to be successful in large scale machine learning...
Sep. 29, 2016 04:00 PM EDT Reads: 2,401