text:
package layout

import (
	"context"
	"encoding/json"
	"io"
	"io/ioutil"
	"os"
	"path/filepath"
	"runtime"

	"github.com/containers/image/v5/internal/putblobdigest"
	"github.com/containers/image/v5/manifest"
	"github.com/containers/image/v5/types"
	digest "github.com/opencontainers/go-digest"
	imgspec "github.com/opencontainers/image-spec/specs-go"
	imgspecv1 "github.com/opencontainers/image-spec/specs-go/v1"
	"github.com/pkg/errors"
)

type ociImageDestination struct {
	ref                      ociReference
	index                    imgspecv1.Index
	sharedBlobDir            string
	acceptUncompressedLayers bool
}

// newImageDestination returns an ImageDestination for writing to an existing directory.
func newImageDestination(sys *types.SystemContext, ref ociReference) (types.ImageDestination, error) {
	var index *imgspecv1.Index
	if indexExists(ref) {
		var err error
		index, err = ref.getIndex()
		if err != nil {
			return nil, err
		}
	} else {
		index = &imgspecv1.Index{
			Versioned: imgspec.Versioned{
				SchemaVersion: 2,
			},
			Annotations: make(map[string]string),
		}
	}

	d := &ociImageDestination{ref: ref, index: *index}
	if sys != nil {
		d.sharedBlobDir = sys.OCISharedBlobDirPath
		d.acceptUncompressedLayers = sys.OCIAcceptUncompressedLayers
	}

	if err := ensureDirectoryExists(d.ref.dir); err != nil {
		return nil, err
	}
	// Per the OCI image specification, layouts MUST have a "blobs" subdirectory,
	// but it MAY be empty (e.g. if we never end up calling PutBlob)
	// https://github.com/opencontainers/image-spec/blame/7c889fafd04a893f5c5f50b7ab9963d5d64e5242/image-layout.md#L19
	if err := ensureDirectoryExists(filepath.Join(d.ref.dir, "blobs")); err != nil {
		return nil, err
	}
	return d, nil
}

// Reference returns the reference used to set up this destination.  Note that this should directly correspond to user's intent,
// e.g. it should use the public hostname instead of the result of resolving CNAMEs or following redirects.
func (d *ociImageDestination) Reference() types.ImageReference {
	return d.ref
}

// Close removes resources associated with an initialized ImageDestination, if any.
func (d *ociImageDestination) Close() error {
	return nil
}

func (d *ociImageDestination) SupportedManifestMIMETypes() []string {
	return []string{
		imgspecv1.MediaTypeImageManifest,
		imgspecv1.MediaTypeImageIndex,
	}
}

// SupportsSignatures returns an error (to be displayed to the user) if the destination certainly can't store signatures.
// Note: It is still possible for PutSignatures to fail if SupportsSignatures returns nil.
func (d *ociImageDestination) SupportsSignatures(ctx context.Context) error {
	return errors.Errorf("Pushing signatures for OCI images is not supported")
}

func (d *ociImageDestination) DesiredLayerCompression() types.LayerCompression {
	if d.acceptUncompressedLayers {
		return types.PreserveOriginal
	}
	return types.Compress
}

// AcceptsForeignLayerURLs returns false iff foreign layers in manifest should be actually
// uploaded to the image destination, true otherwise.
func (d *ociImageDestination) AcceptsForeignLayerURLs() bool {
	return true
}

// MustMatchRuntimeOS returns true iff the destination can store only images targeted for the current runtime architecture and OS. False otherwise.
func (d *ociImageDestination) MustMatchRuntimeOS() bool {
	return false
}

// IgnoresEmbeddedDockerReference returns true iff the destination does not care about Image.EmbeddedDockerReferenceConflicts(),
// and would prefer to receive an unmodified manifest instead of one modified for the destination.
// Does not make a difference if Reference().DockerReference() is nil.
func (d *ociImageDestination) IgnoresEmbeddedDockerReference() bool {
	return false // N/A, DockerReference() returns nil.
}

// HasThreadSafePutBlob indicates whether PutBlob can be executed concurrently.
func (d *ociImageDestination) HasThreadSafePutBlob() bool {
	return false
}

// PutBlob writes contents of stream and returns data representing the result.
// inputInfo.Digest can be optionally provided if known; if provided, and stream is read to the end without error, the digest MUST match the stream contents.
// inputInfo.Size is the expected length of stream, if known.
// inputInfo.MediaType describes the blob format, if known.
// May update cache.
// WARNING: The contents of stream are being verified on the fly.  Until stream.Read() returns io.EOF, the contents of the data SHOULD NOT be available
// to any other readers for download using the supplied digest.
// If stream.Read() at any time, ESPECIALLY at end of input, returns an error, PutBlob MUST 1) fail, and 2) delete any data stored so far.
func (d *ociImageDestination) PutBlob(ctx context.Context, stream io.Reader, inputInfo types.BlobInfo, cache types.BlobInfoCache, isConfig bool) (types.BlobInfo, error) {
	blobFile, err := ioutil.TempFile(d.ref.dir, "oci-put-blob")
	if err != nil {
		return types.BlobInfo{}, err
	}
	succeeded := false
	explicitClosed := false
	defer func() {
		if !explicitClosed {
			blobFile.Close()
		}
		if !succeeded {
			os.Remove(blobFile.Name())
		}
	}()

	digester, stream := putblobdigest.DigestIfCanonicalUnknown(stream, inputInfo)
	// TODO: This can take quite some time, and should ideally be cancellable using ctx.Done().
	size, err := io.Copy(blobFile, stream)
	if err != nil {
		return types.BlobInfo{}, err
	}
	blobDigest := digester.Digest()
	if inputInfo.Size != -1 && size != inputInfo.Size {
		return types.BlobInfo{}, errors.Errorf("Size mismatch when copying %s, expected %d, got %d", blobDigest, inputInfo.Size, size)
	}
	if err := blobFile.Sync(); err != nil {
		return types.BlobInfo{}, err
	}

	// On POSIX systems, blobFile was created with mode 0600, so we need to make it readable.
	// On Windows, the "permissions of newly created files" argument to syscall.Open is
	// ignored and the file is already readable; besides, blobFile.Chmod, i.e. syscall.Fchmod,
	// always fails on Windows.
	if runtime.GOOS != "windows" {
		if err := blobFile.Chmod(0644); err != nil {
			return types.BlobInfo{}, err
		}
	}

	blobPath, err := d.ref.blobPath(blobDigest, d.sharedBlobDir)
	if err != nil {
		return types.BlobInfo{}, err
	}
	if err := ensureParentDirectoryExists(blobPath); err != nil {
		return types.BlobInfo{}, err
	}

	// need to explicitly close the file, since a rename won't otherwise not work on Windows
	blobFile.Close()
	explicitClosed = true
	if err := os.Rename(blobFile.Name(), blobPath); err != nil {
		return types.BlobInfo{}, err
	}
	succeeded = true
	return types.BlobInfo{Digest: blobDigest, Size: size}, nil
}

// TryReusingBlob checks whether the transport already contains, or can efficiently reuse, a blob, and if so, applies it to the current destination
// (e.g. if the blob is a filesystem layer, this signifies that the changes it describes need to be applied again when composing a filesystem tree).
// info.Digest must not be empty.
// If canSubstitute, TryReusingBlob can use an equivalent equivalent of the desired blob; in that case the returned info may not match the input.
// If the blob has been successfully reused, returns (true, info, nil); info must contain at least a digest and size, and may
// include CompressionOperation and CompressionAlgorithm fields to indicate that a change to the compression type should be
// reflected in the manifest that will be written.
// If the transport can not reuse the requested blob, TryReusingBlob returns (false, {}, nil); it returns a non-nil error only on an unexpected failure.
// May use and/or update cache.
func (d *ociImageDestination) TryReusingBlob(ctx context.Context, info types.BlobInfo, cache types.BlobInfoCache, canSubstitute bool) (bool, types.BlobInfo, error) {
	if info.Digest == "" {
		return false, types.BlobInfo{}, errors.Errorf(`"Can not check for a blob with unknown digest`)
	}
	blobPath, err := d.ref.blobPath(info.Digest, d.sharedBlobDir)
	if err != nil {
		return false, types.BlobInfo{}, err
	}
	finfo, err := os.Stat(blobPath)
	if err != nil && os.IsNotExist(err) {
		return false, types.BlobInfo{}, nil
	}
	if err != nil {
		return false, types.BlobInfo{}, err
	}

	return true, types.BlobInfo{Digest: info.Digest, Size: finfo.Size()}, nil
}

// PutManifest writes a manifest to the destination.  Per our list of supported manifest MIME types,
// this should be either an OCI manifest (possibly converted to this format by the caller) or index,
// neither of which we'll need to modify further.
// If instanceDigest is not nil, it contains a digest of the specific manifest instance to overwrite the manifest for (when
// the primary manifest is a manifest list); this should always be nil if the primary manifest is not a manifest list.
// It is expected but not enforced that the instanceDigest, when specified, matches the digest of `manifest` as generated
// by `manifest.Digest()`.
// FIXME? This should also receive a MIME type if known, to differentiate between schema versions.
// If the destination is in principle available, refuses this manifest type (e.g. it does not recognize the schema),
// but may accept a different manifest type, the returned error must be an ManifestTypeRejectedError.
func (d *ociImageDestination) PutManifest(ctx context.Context, m []byte, instanceDigest *digest.Digest) error {
	var digest digest.Digest
	var err error
	if instanceDigest != nil {
		digest = *instanceDigest
	} else {
		digest, err = manifest.Digest(m)
		if err != nil {
			return err
		}
	}

	blobPath, err := d.ref.blobPath(digest, d.sharedBlobDir)
	if err != nil {
		return err
	}
	if err := ensureParentDirectoryExists(blobPath); err != nil {
		return err
	}
	if err := ioutil.WriteFile(blobPath, m, 0644); err != nil {
		return err
	}

	if instanceDigest != nil {
		return nil
	}

	// If we had platform information, we'd build an imgspecv1.Platform structure here.

	// Start filling out the descriptor for this entry
	desc := imgspecv1.Descriptor{}
	desc.Digest = digest
	desc.Size = int64(len(m))
	if d.ref.image != "" {
		desc.Annotations = make(map[string]string)
		desc.Annotations[imgspecv1.AnnotationRefName] = d.ref.image
	}

	// If we knew the MIME type, we wouldn't have to guess here.
	desc.MediaType = manifest.GuessMIMEType(m)

	d.addManifest(&desc)

	return nil
}

func (d *ociImageDestination) addManifest(desc *imgspecv1.Descriptor) {
	// If the new entry has a name, remove any conflicting names which we already have.
	if desc.Annotations != nil && desc.Annotations[imgspecv1.AnnotationRefName] != "" {
		// The name is being set on a new entry, so remove any older ones that had the same name.
		// We might be storing an index and all of its component images, and we'll want to attach
		// the name to the last one, which is the index.
		for i, manifest := range d.index.Manifests {
			if manifest.Annotations[imgspecv1.AnnotationRefName] == desc.Annotations[imgspecv1.AnnotationRefName] {
				delete(d.index.Manifests[i].Annotations, imgspecv1.AnnotationRefName)
				break
			}
		}
	}
	// If it has the same digest as another entry in the index, we already overwrote the file,
	// so just pick up the other information.
	for i, manifest := range d.index.Manifests {
		if manifest.Digest == desc.Digest && manifest.Annotations[imgspecv1.AnnotationRefName] == "" {
			// Replace it completely.
			d.index.Manifests[i] = *desc
			return
		}
	}
	// It's a new entry to be added to the index.
	d.index.Manifests = append(d.index.Manifests, *desc)
}

// PutSignatures would add the given signatures to the oci layout (currently not supported).
// If instanceDigest is not nil, it contains a digest of the specific manifest instance to write or overwrite the signatures for
// (when the primary manifest is a manifest list); this should always be nil if the primary manifest is not a manifest list.
func (d *ociImageDestination) PutSignatures(ctx context.Context, signatures [][]byte, instanceDigest *digest.Digest) error {
	if len(signatures) != 0 {
		return errors.Errorf("Pushing signatures for OCI images is not supported")
	}
	return nil
}

// Commit marks the process of storing the image as successful and asks for the image to be persisted.
// unparsedToplevel contains data about the top-level manifest of the source (which may be a single-arch image or a manifest list
// if PutManifest was only called for the single-arch image with instanceDigest == nil), primarily to allow lookups by the
// original manifest list digest, if desired.
// WARNING: This does not have any transactional semantics:
// - Uploaded data MAY be visible to others before Commit() is called
// - Uploaded data MAY be removed or MAY remain around if Close() is called without Commit() (i.e. rollback is allowed but not guaranteed)
func (d *ociImageDestination) Commit(context.Context, types.UnparsedImage) error {
	if err := ioutil.WriteFile(d.ref.ociLayoutPath(), []byte(`{"imageLayoutVersion": "1.0.0"}`), 0644); err != nil {
		return err
	}
	indexJSON, err := json.Marshal(d.index)
	if err != nil {
		return err
	}
	return ioutil.WriteFile(d.ref.indexPath(), indexJSON, 0644)
}

func ensureDirectoryExists(path string) error {
	if _, err := os.Stat(path); err != nil && os.IsNotExist(err) {
		if err := os.MkdirAll(path, 0755); err != nil {
			return err
		}
	}
	return nil
}

// ensureParentDirectoryExists ensures the parent of the supplied path exists.
func ensureParentDirectoryExists(path string) error {
	return ensureDirectoryExists(filepath.Dir(path))
}

// indexExists checks whether the index location specified in the OCI reference exists.
// The implementation is opinionated, since in case of unexpected errors false is returned
func indexExists(ref ociReference) bool {
	_, err := os.Stat(ref.indexPath())
	if err == nil {
		return true
	}
	if os.IsNotExist(err) {
		return false
	}
	return true
}

redpajama_set_name: RedPajamaGithub


May 30: This Saturday, let IndiHop introduce you to two of STL's most eclectic neighborhoods and all the great beer within. The beer tasting tour will take you through 50 beer samples in the The Grove and Cherokee Street neighborhoods, with live music, artists and street performers entertaining you on your beer journey. New this year, the beer tour will also include coffee from Sump Coffee, Blueprint Coffee and Goshen Coffee. IndiHop kicks off Saturday, May 30 at 1pm and goes until 7pm, with shuttles running between the two neighborhoods for the duration of the event. For more information, head to indihopstl.com.
4 Hands Brewing Co. has also done a bit of traveling, this weekend ending up out in beautiful Colorado for Oskar Blues Brewing's Burning Can 2015. Lauded as the first "active" beer fest in the country, the day will feature a beer relay, sports competitions, live music and canned beers from 50 different breweries across the country. 4 Hands brought along Contact high, Chocolate Milk Stout and Send Help for samples.


text:
Mother Hips- Harlow's, Sacramento Ca 03/28/2002 Audio
Taped by Jim Mclain.
This was Isaac Parson's last night as the bass player in the band. It was understandably a heavy vibe and the band played like it was their last show. I had recently switched from a cassette recorder to minidisc, the minidisc had a problem of skipping occaionally and creating small gaps in the recording. This recording had several of those glitches in it, I have repaired them as best I could but they are not perfect. This video has been upgraded from the previous upload, repairing another glitch that was missed.
Audio Live Concert
Mover- Harlow's, Sacramento Ca 03/28/2002 Audio
March 26, 2002 August 20, 2020
Thursday- Bottom of the Hill, San Francisco, CA. 3/26/2002 Photos
Equipment Used: Nikon N70, Quantaray 28-85mm lens, Kodak T-Max 400 35mm film
Solea- Bottom of the Hill, San Francisco, CA. 3/26/2002 Photos
The Movielife- Bottom of the Hill, San Francisco, CA. 3/26/2002 Photos
Under Fire- Capitol Garage, Sacramento; 3FF- Sweet Bean, Elk Grove 3/23/02
here's 7 minutes of footage from 2 shows- one is Capitol Garage and I used some serious detective skillz to ID the other place as Sweet Bean in Elk Grove.
From Cory Wiegert's collection
Popgun- Harlow's, Sacramento Ca 03/21/2002 Audio
Jackpot- Harlow's, Sacramento Ca 03/21/2002 Audio
I'd been recording just over a year and had graduated from a cassette recorder to minidisc. There should be some soundboard mixed into this recording but if there is it's at a very low level.
Embrace the End- Capitol Garage, Sacramento, CA. 3/16/2002 Photos
Equipment Used: Nikon N70, Quantaray 28-85mm lens, Kodak Tri-X 400 35mm film
No Regard- Capitol Garage, Sacramento, CA. 3/16/2002 Photos

redpajama_set_name: RedPajamaCommonCrawl


The job you are looking for cannot be found.
© 2013 Pennsylvania School Boards Association, Inc. All Rights Reserved.
PSBA's Career Gateway offers a free job posting service to its members.
Your session will be timeout within 5 minutes. Do you want to continue session?
Your session will be timeout within 30 seconds. Do you want to continue session?


text:
Q: Table Valued Function is returning only one row when the actual result contains multiple rows I have table Clients that contains many columns, however I'm targeting two particular columns ClientId and PIN. The example that I'm going to provide is not making much sense but I'm just learning more advanced SQL (T-SQL) topics and my final goal is something a lot different than what is here.
So I made a function which I would like to return all rows that match certain search criteria. So I have this:
CREATE FUNCTION ufn_NumberOfClients (@ClientId INT)
  RETURNS @retContactInformation TABLE
  (
    -- Columns returned by the function
    ClId int PRIMARY KEY NOT NULL,
    PIN nvarchar(50) NULL
  )
  AS
  BEGIN
    DECLARE
    @ClId INT,
    @PIN nvarchar(50)

    SELECT @ClId = ClientId, @PIN = PIN
    FROM Client
    WHERE PIN LIKE '%7788%'

    IF @ClientId IS NOT NULL
    BEGIN
        INSERT @retContactInformation
        SELECT @ClId, @PIN;
    END;
RETURN;
END

But when I execute the function:
SELECT * FROM
ufn_NumberOfClients(4)

I get only one result. Even though it's a valid result, if I execute just
SELECT * FROM Client
WHERE PIN LIKE '%7788%'

I get 5 results, and the function is returning just the last one.
Two thing which worth mentioning. The example which I use to write the function the ClId int PRIMARY KEY NOT NULL, from the table is not DECLAREed after that, but I got error if I don't do it. Also, I pass variable, but I think it's not used so it shouldn't affect the behaviour (or at least I think so).
So how can I return all the results matching the search crieria with a function?

A: You actually insert only one row in the table variable right now, Try this instead :
CREATE FUNCTION ufn_NumberOfClients (@ClientId INT)
RETURNS @retContactInformation TABLE
(
-- Columns returned by the function
ClId int PRIMARY KEY NOT NULL,
PIN nvarchar(50) NULL
)
AS
BEGIN

INSERT INTO @retContactInformation
SELECT ClientId, PIN
FROM Client
WHERE PIN LIKE '%7788%';

RETURN;
END

redpajama_set_name: RedPajamaStackExchange


Ever turned up to work after a long weekend and wished you had three days off every week?
For the employees of New Zealand-based business Perpetual Guardian, the dream has just become a reality.
The trust company has over 200 employees, many of them engaged in customer service roles. Interestingly, the company's founder, Andrew Barnes, doesn't think an extra day away from the office will hurt productivity.
One of the reports Barnes draws from was based on a survey of UK office workers engaged in full-time positions.
The survey asked respondents to report how much time they thought they were productive at work. They also nominated the types of activities they engaged in during non-productive hours.
The average worker felt they spent two hours and 53 minutes of their day being productive, with the largest amount of non-productive time spent checking social media (47 percent of respondents), checking news sites (45 percent) and discussing out of work activities with colleagues (38 percent).
But Barnes's contention is not that employees are wasting time at work, rather they spend a certain amount of their time concerned with day-to-day issues impacting their lives outside of work.
By offering employees a more flexible arrangement regarding hours worked, Barnes believes they'll feel more engaged at work, which should more than compensate for the fewer hours spent in the office.
"The output we want to be interested in is productivity. As an employer, I'm paying for outputs, not the amount of time each employee spends in their chair," said Barnes.
As part of the six-week trial, the team at Perpetual Guardian will present a case study centred on increasing productivity by working fewer hours.
In this sense, Perpetual Guardian is testing a doubly-radical initiative – a process informed and implemented from the bottom of the company up, which places ownership in the hands of each employee.
READ: Is the future of work… less work?
While this system may not work for every organisation (in fact, it may not work for this one), Perpetual Guardian nevertheless has all the features and challenges of a larger business that make it an ideal case study: a physical retail footprint, five-days-per-week opening hours, and a varied workforce that includes a significant number of remote workers.
"We have 16 retail outlets across New Zealand, so we're going to be creating rotating rosters to ensure there's no loss of customer service," said Barnes. "But we're also making this as flexible as possible for our staff.
And with such a radical experiment already gaining attention across the media landscape, Barnes notes his employees are already feeling the pressure to prove themselves.


text:
Train 18 latest update: Launch of Indian Railways' engine-less train delayed further; here's why
By: Devanjana Nag |
Published: January 22, 2019 12:28:06 PM
As the highest electrical authorities in Integral Coach Factory (ICF), as well as the Research Design and Standards Organisation (RDSO), had duly certified Train 18 several times, the rolling stock department pointed out that there was no legal or administrative basis to call for EIG inspection.
The 'Shatabdi killer' will be inspected by the Electrical Inspector to the Government (EIG).
Train 18 latest update: Indian Railways' engine-less self-propelled train set, slated to be first flagged off by December-end, has gone into a loop of delay, with the electrical department set to inspect it. According to an IE report, the 'Shatabdi killer' will be inspected by the Electrical Inspector to the Government (EIG), the Railway Board decided on Monday. As per law, railway rolling stock is exempted from such inspection, however, the Railway Board took the decision despite contrary views from its own rolling stock department, the report said. As the highest electrical authorities in Integral Coach Factory (ICF), as well as the Research Design and Standards Organisation (RDSO), had duly certified Train 18 several times, the rolling stock department pointed out that there was no legal or administrative basis to call for EIG inspection.
According to railway officials, the product was undergoing "procedural evaluation". While the Northern zone of Indian Railways has been instructed to organize the inspection by EIG, sources quoted in the report stated that there will be two procedural problems in the inspection by EIG. First, the inspection by EIG is carried out before an electrical system is charged with electricity. In Train 18's case, it has been charged long back for successful trials. Moreover, certification to that effect has been already issued. Second, to inspect railway rolling stock, the EIG does not have the jurisdiction as it is the domain of the Commissioner of Railway Safety, they said.
Train 18, unlike other rolling stock, is a 25 kv electrical system, and therefore "no sane person" would overrule the Commissioner of Railway Safety after it has flagged a need for EIG inspection, the sources said. In its conditional clearance to Train 18, the Commissioner of Railway Safety had highlighted that the train required clearance from EIG.
According to the Railway Board, all the recommendations of the Commissioner of Railway Safety will be adhered to in entirety. This can delay the flagging off of the train because one of the recommendations is to conduct the crucial oscillation trials again, where train coaches are tested by running them with weights as well as in an empty state. According to the report, these trials took three weeks, last time. Usually, these trials take months. A railway official was quoted saying that even if the railways hurry up the process, it might take double the time duration it took earlier.
Train 18 is slated to run between Delhi and Varanasi, covering the over 700 kilometres distance in around 8 hours. Prime Minister Narendra Modi is expected to flag off the next-generation offering from Indian Railways.


text:
Q: Save http stream video android For one of my android projects I need to implement saving of video from HTTP stream (right now I am just show live stream video to user).
I google that problem and find some solution, I can use FFmpeg. But FFmpeg is c++ library.
Is there are some easy way to save video from HTTP stream?


ANN ARBOR, Mich., May 5, 2018 – EOTech, an L3 company, announced today that it has received the National Rifle Association's (NRA) Golden Bullseye Optic of the Year award for its Vudu™ 1–6x rifle scope. The award was presented on Friday, May 4, by Mark Keefe, Editor-in-Chief of American Rifleman, at the NRA's Annual Meetings and Exhibits in Dallas, Texas.
"This is the first Golden Bullseye Award American Rifleman has presented to EOTech, and the Vudu 1–6x is more than worthy of the prestigious award. It is an innovative solution for both medium- and close-range target acquisition," said Keefe.
The recipient of numerous accolades since its release in 2017, the Vudu line of rifle scopes combines durability, precision and versatility. The line includes six different models in configurations ranging from 1–6x24mm up to 5–25x50mm.
Compact in stature, but loaded with features, the 10.63-inch, 20.1-ounce Vudu 1–6x is equally at home on an AR-style rifle as it is on a favorite deer gun. The first focal plane-illuminated Speed Ring reticle allows for fast target engagement at low power. At high power, a holdover reticle provides markings for sure holds out to 600 yards. The glass inside the Vudu 1–6x's 30mm tube boasts excellent light transmission, resolution and edge-to-edge clarity for optimized target acquisition in any light conditions.
EOTech delivers cutting-edge technology and products, including holographic sighting systems, tactical lasers, and thermal imaging and night vision equipment. The company is dedicated to providing high-quality, ruggedized products for military, law enforcement and commercial markets around the world. Visit www.eotechinc.com to learn more.


Friends at Roose station have now completed replanting to give the station a real Spring feel. The six individual containers are now beginning to come into bloom, adding lots of colour and interest.
Just to let you know that the railway footbridge for Millom is closed at the moment for refurbishment but should re-open in May. Looking forward to see the bridge improvements for this lovely station!


text:
Canadian Forces Intelligence Branch, the first 36 years
Harold A. Skaarup, CD2
Former Honorary Lieutenant-Colonel for 3 Intelligence Company (Halifax)
When the 36th Anniversary of the Intelligence Branch being celebrated in October 2018, there will be much to be proud of looking back on our accomplishments. When the newly formed Intelligence Branch formally stood up on 29 October 1982, there were 88 Intelligence Officers and 195 Intelligence Operators for a total of 283 in the Regular Force and an additional 24 Reserve Intelligence Officers and 50 Intelligence Operators officially serving.[1] The primary adversary faced by Canadian soldiers at that time was considered to be the Soviet Union, and serving intelligence personnel were actively engaged in the Cold War. Today, there are more than 400 Intelligence Officers and well over 600 Intelligence Operators in service around the globe. The Soviet Union no longer exists and many Intelligence Branch members are engaged in a hot war in Afghanistan carrying out the fight against global terrorism.
Authors David Stafford and Rhodri Jeffreys-Jones wrote, "the intelligence relationship between three important North Atlantic powers (Canada, the UK and the US) in the Twenty-first century, from [the Second World War] to post-Cold War… cemented loose and often informal inter-allied agreements on security intelligence that had preceded it, and created new and important areas of close and formal co-operation in such areas as code-breaking and foreign intelligence. Anglo American SIGINT, the OSS/SOE connection, the Venona intercepts and the unmasking of Alger Hiss, Harry Dexter White, and the defection of Igor Gouzenko", are a few examples of this co-operation.[2]
Things have changed, but nowhere in the CF is this more evident than in our Intelligence Branch. In 1982, we had just come out of an integrated Security Branch facing a single almost overwhelmingly clear adversary, with the remote possibility in the age of Mutually Assured Destruction (MAD) and détente, of global annihilation in a nuclear war. In October 1989, just seven years later, the Berlin Wall fell and shortly afterwards many Eastern European nations separated from the former Warsaw Pact and joined the West. The peaceful period lasted for what seemed to be only fractions of a second. Members of the CF abruptly found themselves switching from peacekeeping duties to war fighting in Croatia, Bosnia-Herzegovina, Somalia, Kosovo, Rwanda, and East Timor in a series of increasingly dangerous missions, all of which required the direct involvement of fit and alert intelligence staffs. Today, more Canadian intelligence personnel are directly involved in, or are providing background support to the war in Afghanistan than existed in the entire CF in 1982. We live in interesting, and in some respect, very dangerous times. What we do, therefore, makes a tremendous difference, more so than perhaps in the days of the Cold War.
Looking back at the series of changes Intelligence has undergone, one of the most significant administrative events took place when the amalgamated Security Branch was formed in 1969 because of the CF integration unification policy put into effect on 1 February 1968. The Security Branch included all police, security and intelligence personnel from the various Corps and Branches of the former three services. On paper, this seemed workable. In practice, it proved difficult, and various studies led to the conclusion that separate Security and Intelligence Branches were required. The CIS fully endorsed this conclusion, as did the Vice Chief of Defence Staff, which led to the formal announcement of the separation of the Security Branch in CANFORGEN message 32/81 3 December 1981. The newly created Intelligence Branch included the establishment of the Intelligence 82 Officer classification and the Intelligence Operator 111 trade.
During the formation of the Intelligence Branch Col Victor V. Ashdown (in his role as the first Intelligence Branch Advisor), wrote that the immediate reasons for a separate Intelligence Branch were, "the obvious difference in tasks of Police/Security and intelligence personnel, and the strong desire for a separate identity among the Intelligence Group. However, underlying these reasons is the realisation by our Generals and Admirals that intelligence as a function is becoming more important. There is also a definite trend away from the days of unification/integration – it is now OK to talk about war, traditions and "the military ethos."
Our first Honorary Colonel Commandant, Sir William S. Stephenson stated, "today, intelligence in the context you are aware of, is not only the first line of defence but might very well be the only defence. We must know before the event when the enemy intends to strike and thereby strike him first."[3]
Intelligence Branch personnel have been involved in the mainstream of many military operations world-wide since its inauguration in 1982. Intelligence Branch members at that time were employed overseas with the CDLS in London and in Washington; with SHAPE in Belgium, and with the CFAs in Beijing, Belgrade, Warsaw, Prague, Moscow and Tel Aviv. There were also many undergoing training at the Canadian Forces Language School (CFLS) in Ottawa. Intelligence Branch personnel were serving at CF Bases (CFB) in Germany with 1 Canadian Air Group (1 CAG) at CFB Baden-Soellingen and with 4 Canadian Mechanized Brigade Group (4 CMBG) in Lahr, and in other locations in Canadian Forces Europe (CFE) and across Canada.
The Intelligence Branch continued to evolve as new direction and planning was provided. Branch Boards wrote Mobilisation Specifications for Military Occupation Code (MOC) 82 and Intelligence Operator 111. These codes were subsequently used as a basis for new Intelligence Reserve Specifications, which were prepared by Force Mobile Command (FMC) HQ. The Counter Intelligence role was retained by the Security Branch, the consequences of which are still being debated. A Combat Intelligence study was carried out for Army Combat Development, outlining the future organization of Army Intelligence. FMC HQ gained its own Intelligence organization, Intelligence positions in CFE grew, and an alliance was formed with the British Intelligence Corps.
The CF Intelligence Branch Association was formed on 1 May 1985, and shortly afterwards, Intelligence Branch numbers were issued and a Branch Historical Committee was formed. As the various commands began to demand more intelligence support for their operations, women were re-mustered into the trade as Intelligence Operators. These demands challenged the training system, as it takes a fair amount of time to integrate newly trained Intelligence Officers and Operators. An unprecedented recruiting drive took place in the 1980s to increase personnel in the Intelligence trade. The Reserve shortfall was particularly acute, with 363 Army slots being set aside for FMC alone in 1985, whereas Army Intelligence Militia numbers stood at only 40 personnel at the time. Air Command and Maritime Command also continued to expand the number of Intelligence positions on their establishment.
The provision of training programs to meet the professional requirements of the modern Intelligence Officer and Intelligence Operator continued as a top-level Branch priority. Courses being conducted by the Intelligence Training Company at CFSIS included Intelligence Officer 82A, Intelligence Operator TQ5A, Intelligence Operator TQ6A, Intelligence Operator TQ6B, Interrogator, Combat Intelligence Officer, Combat Intelligence NCO, Air Intelligence and Reserve Intelligence courses.
When Sir William Stevenson retired, MGen Reginald J.G. Weeks, CD, was offered and accepted the post of Honorary Colonel Commandant of the Intelligence Branch on 10 October 1985. Expansion in every department of the Canadian Forces seemed to be the norm, as the Chief Intelligence and Security (CIS) adopted a new organization with two Divisions: Director General Intelligence and DG Security. DG Intelligence retained Director Defence Intelligence (DDI, Director Scientific Intelligence (DSTI), DISA and PPC, and gained a Director of Current Intelligence (DCI) (formerly DDI 5), and a Director of Imagery Exploitation (DIE), (formerly DDI-6). DDI sections were renumbered and CIS OP&T was renamed Director Intelligence Plans and Doctrine (DIPD). These changes increased the demand for trained personnel, just as more Intelligence establishment positions were being added at NORAD in Colorado Springs; Elmendorf AFB, Alaska; the Combat Training Centre (CTC) at CFB Gagetown; and at CF Communications Command (CFCC) HQ in Ottawa. Recruitment and training of Intelligence personnel for the Reserve Electronic Warfare Squadron in Kingston also began.
Throughout this era, many Intelligence personnel will remember taking part in the various RENDEZVOUS Exercises held in the field at CFB Gagetown and CFB Wainwright and with Command Post Exercise workups at CFB Petawawa and CFB Valcartier. Over the same period, Air Command Intelligence Operators were heavily engaged in MAPLE FLAG exercises at CFB Cold Lake while supporting counter-Bear Intruder Operations in the far North. Intelligence staffs supporting the Navy took an active part in MARCOM and MARPAC exercises at sea and supported sovereignty patrols and live operations against the submarine threat. All of these concurrent activities kept Intelligence personnel in every Command very busy with their analysis and assessment taskings.
The Intelligence Collection and Analysis Centre (ICAC) concept was developed through the Army's Combat Development Process (as it was known in those days) within the context of the well-known "Corps 86" plan. The first ICAC was deliberately fielded during the RITE SIMPLE/RITE COMPLEX series of command post exercises in Valcartier in 1985. It was subsequently deployed as part of the FMC Division during RV 87 (Apr-Jun) in Wainwright and, as in the Valcartier exercise, it brought together "Battle Analysts", Meteorologists, Terrain Analysts, feeds from the Experimental RPV troop, Air Photo Reconnaissance, Electronic Warfare, reporting from the deployed Interrogation Team as well as Long Range Patrols – all under one roof. This was the first true deployment of an "All Source" Intelligence Centre with actual collection carried out against "real" targets. It also involved the early use of computers (with the then very modern Apple IIe) for collection management/ sensor co-ordination planning, analysis, data-base management, etc. The lessons learned were captured in the 1988 version of the well-worn "Combat Intelligence" 315 (2) publication written by then Maj G.W. Jensen, Lieutenant J.A.E.K. Dowell and Lieutenant K.A.V. Sutton. This was the foundation leading to the establishment of 1 Division Intelligence Company in 1989 - with an integral ICAC Platoon. This was one of the most profound changes in Army Intelligence since WWII and has, indeed, led to the formation of the currently deployed ASIC (in the world of Special Operations Forces, the Special Operations Intelligence Centre). It has been suggested that the ASIC/SOIC construct is an "evolution" of the ICAC concept (a mix of strategic and tactical) rather than a revolution. In other words, the ground work for the success of the ASIC/SOICs in battle was developed twenty years ago.
Exercise FINAL DRIVE evolved at CFB Kingston, with the participation of many Intelligence staffs brought in to support the final course completion exercises at "Foxhole U." The first Intelligence Operators trained to support a specifically created Communication Reserve Unit, the Intelligence Troop, Electronic Warfare Squadron, 763 Communication Regiment, graduated in 1987. By the 5th Anniversary of the Intelligence Branch, the Canadian Forces requirements for Intelligence personnel had expanded considerably (87%), as a new Defence White paper was being tabled.
In 1988, the Nobel Peace Prize was awarded to all United Nations peacekeepers, which at that time included the majority of serving Intelligence Branch personnel. The Peacekeeping medal recognising this service would not be awarded until 2000. While supporting the myriad demands of training and operations, Intelligence Branch personnel continuously updated their professional development skills. They took advanced training on courses in such subjects as Soviet Operational Doctrine, Imagery Interpretation, Electronic Warfare Analysis, Prisoner of War Handling (PW), & Tactical Questioning Methodology, NATO Air Ground Operations Joint Intelligence Staff Intelligence, Psychological Operations (Psy Ops), and Targeting Procedures.
In 1989, 1st Canadian Division (1 Cdn Div) Intelligence Company was formed at CFB Kingston to support the modernised Army "Field Force." The new Division was tasked as the Central Army Group (CENTAG) Reserve, while a Territorial Defence Force was to be responsible for the defence of North America.
The First Gulf War began at 0100 hours on 17 January 1991, as America and its allies launched their opening strikes against Iraq with Tomahawk cruise missiles and aircraft. The First Gulf War engaged a significant number of Canadian Intelligence Branch personnel, both through deployments and in the Intelligence analysis of the situation which precipitated the war. That summer, a series of events at Oka and Akwesasne in Central Canada took place, leading the Canadian Government to deploy forces in an Aid to the Civil Power Operation. During the difficult and often tense operations that followed, Intelligence personnel were in continuous demand, and they became well-recognised for their valuable contributions.
Following the demise of the Soviet Union and reduction in Cold War tension, the Canadian people demanded to see a "peace dividend." Not long afterwards, the government announced a series of budget cuts to the Canadian Forces, resulting in the termination of services by 1 Combat Air Group (CAG) and 4 Canadian Mechanized Brigade Group (CMBG) in Europe. The last major Air and Brigade elements of Canadian Forces Europe (CFE) were repatriated to Canada by 1993. As open skies policies began to be implemented, many Canadian Intelligence personnel were trained as Arms Verification Inspectors, and subsequently deployed to a wide number of countries, from Iceland to Russia to count and verify the status of various weapons and equipment. Although the majority of Canada's peacekeepers with the UN in Cyprus were also withdrawn, Canadian Forces Intelligence personnel continued to serve with the UN HQ in Nicosia, Cyprus.
In October 1991, Canadian Forces Intelligence personnel deployed overseas at the request of the Committee of Security and Co-operation in Europe (CSCE), to participate in the European Community Monitoring Mission (ECMM) in Yugoslavia. With an expansion of the Intelligence staffs employed at Tunney's Pasture in Ottawa, a number of these personnel were made available for temporary deployment duties overseas. In addition, in October, celebrations were held marking the 10th Anniversary of the Intelligence Branch and the 50th Anniversary of the Canadian Intelligence Corps. Some 300 participants took part in the commemoration at CFB Borden in 1992.
From December 1992 to June 1993, Canada participated in the Unified Task Force (UNITAF), a United States-led enforcement coalition dealing with the civil war in famine-ravaged Somalia. Many members of the Intelligence Branch served with the peacekeeping forces in Mogadishu during this mission. In 1993, Intelligence personnel found themselves deployed for operations in the dangerous environments of Croatia and Rwanda. In a number of cases, our Intelligence crews were tasked to investigate incredibly grim atrocities in both regions, with extremely large numbers of casualties to examine both during and following the genocide in Rwanda.
In February 1993, 2 Intelligence Platoon comprised of both regular and reserve members, stood up in Ottawa. In January 1994, the Canadian Forces School of Intelligence and Security (CFSIS) stood up the Distance Learning Company. In October 1995, the Intelligence Training Company at CFSIS was reformed.
A great number of Canadian Forces Intelligence personnel have rotated through the various Intelligence positions in Bosnia-Herzegovina beginning in 1992 and continuing to the present day. Canadian Intelligence personnel were part of the Peace Implementation Force (IFOR) and its follow on, the Peace Stabilization Force (SFOR), in the Former Yugoslav Republic (FYR) from the beginning. The Canadian National Intelligence Centre (CANIC) based in Sarajevo, provided Intelligence support to NATO through the HQ Allied Rapid Reaction Corps (ARRC) Main, the Commander Canadian Contingent in-theatre (CCIFOR, and later CCSFOR), and national decision-making bodies concerned with the future of the FYR.
Many Intelligence personnel participated in deployments to Haiti over a number of missions. In 1996, the Canadian Forces Photo Unit (CFPU) was added to the J2 Division in Ottawa. 10 Tactical Air Group (10 TAG) Intelligence personnel were kept busy with Tactical Helicopter operations and exercises across Canada, and Air Command had its hands full with down-sizing, operations in Vicenza and Ancona, Italy, counter drug operations, BLUE FLAG exercises, deployments, operation support flights to Zagreb, Fish Wars, Joint Intelligence MAPLE FLAG, Haiti, and base closures.
In 1996, Major-General (Ret'd) J.E. Pierre Lalonde, CD2, was appointed as the new Colonel Commandant of the Canadian Forces Intelligence Branch. Army HQ returned to Ottawa on 3 September 1996, moving into the top three floors in NDHQ's North Tower. The Commander's G2 staff became officially known as Director Land Force Readiness 4 (DLFR 4).
Enemy, weather and terrain have always been the big three when it comes to determining Intelligence priorities. When a major ice storm hit parts of Ontario and Quebec in 1997 knocking out power in large parts of the provinces, Intelligence was of critical importance. In April 1997, Air Command Intelligence staffs were also tasked to support OP ASSISTANCE, the Canadian Forces operation to battle the Red River Flood.
Change continued to take place in the Canadian Forces, and in 1997, Brigadier-General Ken C Hague stated, "The hallmark of the Canadian Forces, and by extension the Intelligence Branch, has been turbulence, constant change, and uncertainty for the past several years. Re-engineering, personnel and budget reductions, rapid advances in information technology and management (IT/IM), social change, media attention, and numerous other factors have influenced our military culture and mores, some would argue, more than at any other time in the history of the CF…In addition to experiencing this change phenomenon, we have also been the subject of an extraordinary volume of operational and professional challenges, which have taxed our diminishing resources to the limit: Bosnia-Herzegovina, Haiti, Zaire, Guatemala, greater Intelligence opportunities, increased demand and requirements, more sophisticated clients who are product smart, and increased demands on fewer managers."
Brigadier-General Hague observed that one of the keys to future success in the Intelligence world is to take a proactive approach to keeping ahead of the IT/IM power curve. He also noted that the missions in both Haiti and Bosnia-Herzegovina confirmed the invaluable role played by human Intelligence (HUMINT), pointing out that eighty percent of all Intelligence used by commanders in these missions was derived from HUMINT sources. He added, "the National Intelligence Cell (NIC) concept utilised primarily in Bosnia-Herzegovina had proven extremely beneficial to both NATO commanders and home nations."
This situation continues to apply today, as he said, "Our challenge must be to exploit each and every new gadget and tool to the fullest by looking and thinking outside the box of conventional operational practices. This challenge is not a simple or easy one. It requires inquiring minds at the coal-face, and encouragement and recognition by supervisors." Brigadier-General Hague encouraged all Intelligence personnel to "respond to the challenges we all face by committing yourself to continuous self-improvement, to exploiting IT/IM to the fullest, and to search for methods of maximising the return on Canada's investment on the military Intelligence function.[4]
In 1997, the SI/CI functions of DG Security and Military Police were transferred to J2/DG Intelligence in Ottawa. The change meant that "Security Intelligence" was now under control of J2 Operations, "CI doctrine and planning" under J2 Plans and Policy, and the 40-person National Counter Intelligence Unit (NCIU), reported directly to J2/DG Intelligence.
In 1998, Intelligence Branch personnel worked in both of NATO's major Commands, including Supreme Allied Command Atlantic (SACLANT), close to the major naval base at Norfolk, Virginia; and Supreme Headquarters Allied Powers Europe (SHAPE), in Mons, Belgium.
In 1998, CFSIS was split Into the CF Provost School and the CF School of Military Intelligence (CFSMI), with their commandants holding the rank of Major. That same year four East European Bloc students attended the Advanced Intelligence Course, an incredible change in light of events of the previous decade. The universal threats at this time were considered to be drug trafficking, international gangsterism, and Y2K. Identifying personnel for CF operations continued to be a challenge for the Land Forces Intelligence community, exacerbated by high demand, fewer postings and unforecast attrition. The lack of deployable personnel at the rank of Captain, Warrant Officer and Sergeant, and in particular, bilingual personnel, caused the most difficulty. The Air Command Intelligence Community was approached for assistance.
In 1998, Intelligence Officers were loaded onto the year-long Technical Staff Course in Kingston for the first time, adding a new range of diverse and useful training to the Branch skills and knowledge base.
A landmark event took place on 17 June 1999 at 1800 hours, when CFSIS ceased to exist. Lieutenant-Colonel Tony Battista handed over the Security and Military Police functions to Captain Jim Legére, as Commandant of the Canadian Forces Military Police and Security Academy (CFMPSA) and the Intelligence function to Major Robert G. Nash as Commandant of the CF School of Military Intelligence (CFSMI). CFSMI's move to CFB Kingston took place the following year, in 2000.
As the threat continued to evolve, so too did the Intelligence Branch. In 1999, Colonel Pat Crandell made the assessment that "the next millennium would bring with it further disintegration of the nation state, criminalization of some countries, inter-economic bloc friction, religion-based conflict, and regional hot wars. The millennium would also bring incredible new challenges and opportunities driven by the revolution in military affairs which itself is being fuelled by quantum leaps in technology. Knowledge-base warfare is the new reality. The challenge is to adjust quickly enough and invest enough in systems and our people to remain interoperable with our primary allies."
Colonel Patrick Crandell predicted, "the conflict in the next century and beyond would be radically different, where the first round down range would likely be a logic bomb, as opposed to a GBU 12." He suggested that it would be a conflict where "a smaller adversary could inflict potentially campaign-stopping damage through asymmetric attack. It would also be a conflict where, more than ever before, success would hinge on the side with the best Intelligence capabilities. To fight and win in such an environment will require both evolutionary as well as dramatic changes in our doctrine, structures, collection and processing capabilities, and in the education and training of our people."
Colonel Crandell believed, "the future will bring fewer Intelligence organisations, but those that remain will see dramatic increases in capability and scope of responsibility, driven by massive new data flows made possible through ever advancing technologies. It will not be that many years before we are capable of 24/7 global surveillance. Think of what that means from the perspective of future C3I. How many headquarters will we need, or more to the point, will we be able to afford in such an environment? What happens to our traditional concepts of C2, when one headquarters in Canada will be able to provide tactical threat warning to deployed forces and indeed control those forces? In this environment, Intelligence organisations will need to be truly all source in their analyses and will contain Imagery, signals, and human and Counter Intelligence specialists possessing advanced analytical training and driving "Intelligence" IT systems. They will present their analyses graphically in a Geospatial context so that the user will be able to visualise the issue of concern in the actionable space for which they are responsible. The other potential I see is that the traditional division between "Ops and Intelligence" will blur, with Intelligence taking on more and more of the responsibility for red, blue, and grey situational awareness and display… Change, whether it is gradual or radical, and whether we like it or not, will be our constant companion."
The pace of operations overseas grew exponentially, as at one point in 2000, there were 4,400 personnel deployed on twenty-two missions, more than at any time since the Korean War. Intelligence Branch personnel found themselves at opposite ends of the world, with OP KINETIC underway in Kosovo and OP TOUCAN being played out in East Timor. There were for example, twenty-three Intelligence personnel in the Balkans (fifteen in Bosnia-Herzegovina and eight in Kosovo), two in the Central African Republic; and four in East Timor at any given time. Aside from the hazards of being in a war zone, Intelligence personnel had to contend with many cases of tropical diseases such as malaria, Dengue fever and diarrhoea.
CFSMI staffs took their instructional expertise on the road as well, and following a request from the Zimbabwe Defence Forces (ZDF), a three-man team of CFSMI instructors was formed to conduct a three-week Strategic Intelligence Course in Harare, Zimbabwe. Canadian Intelligence personnel also conducted a course in Prague, in the Czech Republic.
Attrition continued to pose a significant numbers problem for the Intelligence Branch as demands for its services increased. In 1999, Branch strength was 160 officers and 247 NCMs in the Regular Force, and the Reserves were authorised 148 positions, but were under-strength at all rank levels, even though 225 positions were planned for the following year.
In 2001, Major-General J.E. Pierre Lalonde ended his five-year role as the Colonel Commandant of our CF Intelligence Branch. He was succeeded by Major-General (Ret'd) C. William "Bill" Hewson.
Some 460 CF personnel were deployed to Eastern Africa following the cessation of hostilities between Ethiopian and Eritrean forces and the inauguration of the United Nations Mission in Ethiopia Eritrea (UNMEE). Intelligence Branch personnel were part of Canada's contribution to this mission, finding themselves in Eritrea, located in the Horn of Africa, participating in "Military Information" operations.
In anticipation of future requirements, J2 Imagery and the CF Photographic Unit (CFPU) were fused into a single entity, re-emerging on 21 June 2001 as the CF Joint Intelligence Imagery Centre (CFJIC).
NORAD personnel continued to monitor the threat posed by the vast rocket and strategic air assets of the former Soviet Union, as well taking part in operations in support of surveillance and control of the airspace of Canada and the USA for the purpose of sovereignty and defence. Then on Tuesday, 11 September 2001, the world as we knew it in North America changed dramatically. The events of this day have come to be known as the 911 terrorist attacks.
Between 7:45 a.m. and 8:10 a.m. EDT on that date, four airplanes were hijacked from East Coast airports in the USA. At 8:46 a.m. EDT, the first hijacked passenger jet crashed into the north tower of the World Trade Centre in New York City, tearing a gaping hole in the building and setting it on fire. At 9:03 a.m. EDT, a second hijacked airliner crashed into the south tower of the World Trade Centre and exploded. At 9:43 a.m. EDT, a third crashed Into the Pentagon, sending up a huge plume of smoke. At 10:10 a.m. EDT, a fourth hijacked airplane crashed in Somerset County, Pennsylvania, Southeast of Pittsburgh. At 10:24 a.m., the FAA reported that all inbound transatlantic aircraft flying into the United States were being diverted to Canada. Within hours, US officials reported Saudi militant Osama bin Laden, who was suspected of co-ordinating the bombings of two US embassies in 1998, was involved in these attacks.[5]
On 12 September 2001, a day after the terrorist attacks in the United States of America, NATO invoked the principle of Article 5 of the Washington Treaty. After confirming that such actions had been conducted from abroad, the Article became operative on 2 October 2001. Bin Laden's home base was known to be in Afghanistan at that time and in due course, Canadians Forces Intelligence personnel found themselves on the ground participating in the hunt for him. We continue to be there with the International Security Assistance Force (ISAF) based in Kandahar and Kabul at the time of writing.
OP APOLLO was Canada's military contribution to the International campaign against terrorism, initially consisting of one warship. In co-operation with vessels of the OP ENDURING FREEDOM coalition, the frigate HMCS Calgary conducted maritime interdiction operations in the Arabian Gulf.
In the wake of the events of 11 September 2001 and the Canadian involvement in the Global War on Terrorism, the first CF offensive combat operations since the Korean War were conducted from February 2002 to July 2002, with the deployment of 3 Princess Patricia's Canadian Light Infantry (PPCLI) Battle Group (BG) to Kandahar, Afghanistan. Also for the first time since Korea, a Canadian Army unit was integrated under an American unit, in this case 187 Brigade Combat Team, 101st Airborne Division (Screaming Eagles), for combat operations. This deployment included Intelligence contributions on a scope quite different from previous operations. Intelligence personnel were deployed as part of the offensive units in order to maximise immediate exploitation of any information gathered in situ.
Author Michael J. Cole accurately described the situation in Canada in the years following these horrific terrorist attacks: "Nothing has captured our imagination and fed our nightmares since 11 September 2001, more than international terrorism. The news is filled with "terror," and our government, from the prime minister to security experts, have repeatedly told us that for Canada, it is no longer a question of "if," but "when."[6] Dwight Hamilton also noted that, "Since 9/11, Canada has been on the front lines of a New World Order that few understand. And in today's world, secret intelligence is not just the first line of defence - it may be the only one."[7] David Last and Bernd Horn noted that, "Twenty years from now, security issues may dictate that counter-terrorism is more important than operations to secure stability and rule of law. Security at the border, ethnic demography, and the perspective of the next generation will determine what strategic choices Canada will make about special military operations and the elite forces developed to carry out special missions."[8]
On the 20th Anniversary of the Intelligence Branch, Major Jim Godefroy noted we had "evolved from a nascent organization that was oriented towards Cold War enemies to one that provided Integral and highly sought-after support to every Canadian Forces deployment. Intelligence Branch personnel were serving in many offices within National Defence Headquarters; at the CF Joint Intelligence Imagery Centre (CFJIC); in the Joint Intelligence Operations Group (JOG) at CFB Kingston; in Land Force Command, Area, Brigade Group, and Reserve Intelligence units, and Training and Doctrine positions; at 1 Canadian Air Division, Canadian NORAD Region Headquarters and in eight of fourteen Air Force Wings; with the Navy on both coasts; in national battle group and contingent headquarters on overseas missions; and with multi-national division and mission headquarters in United Nations or NATO areas of operations. Army and Air Force Reserve Intelligence personnel had won honours and awards, deployed on countless operations, and trained incessantly to meet future operational requirements. Naval Intelligence staffs ran state of the art watch centres, and deployed to sea in ships and naval task groups in support of national and coalition operations. Air Intelligence staffs provided support to operations, including those of NORAD, in tactical helicopter, fighter, maritime patrol and helicopter, and transport squadrons. Canadian Forces Intelligence liaison officers worked to enhance connectivity with Canada's allies and other government departments. Intelligence Branch personnel continue to serve abroad in NATO and NORAD positions, providing allies with tangible support while increasing our profile and reputation abroad."
Branch personnel served with distinction in support of numerous coalition operations with the United Nations and NATO in many regions of the world, including Cyprus, Western Sahara, the Persian Gulf, Somalia, Croatia, Bosnia-Herzegovina, Kosovo, Macedonia, Rwanda, Sierra Leone, the Central African Republic, Ethiopia-Eritrea, East Timor, Afghanistan and Haiti. They supported disaster relief efforts in Central America and Turkey, and domestic operations (Dom Ops) during Manitoba's flood (1997), central Canada's ice storm (1998), the Swiss Air disaster (1998), Y2K contingency planning (1999), and the 911 response (2001). Intelligence Branch personnel served on almost every major operation undertaken by the Canadian Forces during the last 20 years. Invariably, they produced excellent results and provided first-rate support that far exceeded their numbers and resources.
In 2002, the Director General Intelligence noted that an audit done on Canadian Forces Intelligence by the Chief of Review Services indicated that there were 2000 personnel doing "Intelligence" in the Canadian Forces, but only 400 actually wore an Intelligence Branch cap badge. A requirement was identified for a central "Intelligence" authority within the Canadian Forces. He reported improvements in Intelligence included the development of an Integrated Intelligence, Surveillance and Reconnaissance (ISR) capability, which strengthened the link between analysts and their sensors up to the key decision makers. ISR developments including enhanced sensors on ships and improved shore support capability were underway in the Navy in order to improve support to fleet operations. The Air Force was engaged in a CF ISR/Joint Intelligence Space Project, including an improved Imagery capability and a CF Fusion Centre (all-source cell). Army Intelligence Reserves were in a healthy position. Air Force and Army Reserve positions had nearly doubled (filled by mainly ex-Regular Force personnel). The Naval Reserves changed their Naval Control of Shipping MOC to Reserve Naval Intelligence.
In 2003, Intelligence personnel served in the J2 Section of the Canadian Joint Intelligence Task Force South West Asia (CA JTFSWA) National Command Element (NCE) working at the US Central Command HQ at MacDill Air Force Base, Tampa, Florida, as part of OP APOLLO. Many Intelligence Branch personnel had served and would likely serve again on OP ATHENA in Kabul, Bagram and Kandahar, Afghanistan. Intelligence personnel were also at sea, assigned to assist with control of the Northern Arabian Gulf in the vicinity of Iraq, an area that had traditionally been the Area of Operations (AO) for Canadian ships in previous deployments such as OP AUGMENTATION. Training for all these missions intensified at all Canadian Forces bases, with Intelligence personnel included in the preparations for deployment of other Canadian Forces personnel, often while getting ready to deploy themselves.
Domestic Security became a priority, with all elements of the Canadian Intelligence Community working in association with various government agencies, some of them newly created since the events of 11 September 2001. The Intelligence Branch found itself working closely with the Public Safety and Emergency Preparedness Canada (PSEPC), which had taken on the fundamental role of government to secure the public's safety and security. Following its creation on 12 December 2003, PSEPC combined the core activities of the previous Department of the Solicitor General, the Office of Critical Infrastructure and Emergency Preparedness (OCIEP), and the National Crime Prevention Centre. PSEPC is part of the portfolio of Public Safety and Emergency Preparedness that includes the Royal Canadian Mounted Police (RCMP), the Canadian Security Intelligence Service (CSIS), the Correctional Service of Canada (CSC), the National Parole Board (NPB), the Canada Firearms Centre (CFC), the Canada Border Services Agency (CBSA), and three review bodies. In close concert with these agencies, Intelligence Branch personnel participated in numerous training exercises and planning conferences to deal with civil emergencies such as hurricane relief, ice storm damage, forest fire fighting, the possibility of an avian influenza epidemic and of course criminal and counter-terrorism concerns wedged in at all levels.
In 2004, thirty-four Intelligence Branch personnel provided Intelligence in support of the Commander of OP HALO, with most operating out of Port au Prince, Haiti. Canadians also provided continuous Intelligence personnel to the G2 staffs supporting the SFOR Multinational Brigade (North West) headquartered in Banja Luka, Bosnia-Herzegovina.
On 12 November 2004, the Chief of the Defence Staff (CDS) and the Deputy Minister (DM) approved in principle the conclusions and recommendations of the Defence Intelligence Review (DIR) and approved the designation of DG/Intelligence as the Chief of Defence Intelligence (CDI). This change launched Defence Intelligence on a multi-year transformation process that saw it develop a capability that is in a better position to respond to the unprecedented demand for timely, accurate and fully Integrated Intelligence.
As of 2010 there are more than 900 serving members and significant numbers of Intelligence Branch personnel have been deployed in Afghanistan, while many more are expected to do so in support of the Canadian government's commitment to provide Canadian Forces personnel in theatre for some time to come.
Although the CF Intelligence Branch is relatively small in comparison with its allied counterparts, all members work collectively to provide the necessary timely and useful Intelligence to military commanders required to assist them in their decision-making. The Intelligence Branch Advisor has stated that the Branch "can be justly proud of what it has accomplished over the last twenty-five years. We have served quietly with little fanfare, working long hours in austere conditions and always with a single-minded purpose – to provide the commander with Intelligence needed to make operational decisions. We will never go wrong if we maintain this focus, and new members of the Branch can be justly proud of the tradition they have inherited. There will always be new operations, new analysis to be done, and new pages to be written in the history of our Intelligence Branch."
"Our challenge as a Branch will be to continue to provide carefully selected, highly motivated, thoroughly trained and operationally focussed Intelligence professionals capable of expertly applying the Art & Science of Military Intelligence at the tactical, operational, and strategic levels. There is no less of a requirement for the products of the Intelligence cycle now, (and the sharing of them with ones allies) than there was in the age of Napoleon Bonaparte and Field Marshal Arthur Wellesley, 1st Duke of Wellington. The present Intelligence Branch continues the tradition of a long line of Canadian military personnel who have served their country."
"The fact is that although success in battle can most readily be won by accurate information about the enemy, and disaster stumbled into by ignorance, the chances and perils of human life rule the battlefield. There is no sure road to success. In no part of a warrior's work is this truer than in Intelligence." Col Peter E.R. Wright, Canadian Intelligence Corps.
Intelligence is of concern to all members of the Canadian Forces and it continues to be generated and disseminated to commanders at all levels. Virtually every member of the Intelligence branch has been affected by the world events that have taken place following the end of the "Cold War and our subsequent participation in "hot" wars.
In 1982, LCol Victor V. Ashdown stated, "The future of the Intelligence Branch…depends on us. The leadership of the Canadian Forces has noted that the Intelligence function is becoming increasingly important and has decided to re-establish an Intelligence Branch to meet the need. We have been given a vote of confidence by the top echelon…the best guarantee for a bright future is our own professionalism – the ability and the desire to do the job better than anyone else. Ability we can ensure through selection and training, but desire – the difference between an adequate job and an excellent one – must come from within each of us. It must be nurtured by good leadership, a sense of "caring," a common identity and a common purpose. Make a commitment – to yourself, to the Branch and to the Forces – to strive for excellence in everything you do."[9]
There is much that we can be proud of and reflect on in the present day Canadian Forces Intelligence Branch. Branch personnel have become the core of the Defence Intelligence Function and are recognised as true professionals in the Art and Science of Military Intelligence, leading action through knowledge. The Intelligence Branch has truly been taken from out of the darkness and into the light.
E Tenebris Lux
"No where does the maxim "knowledge is strength" more fittingly apply than to the relationship between a commander and his G-2. By looking into the past, HLCol Skaarup has helped ensure that lesson is not lost in the future." John Bryden
[1] On 1 Aug 1982, the Intelligence Branch included 1 Col, 1 A/Col, 5 LCol, 19 Maj, 45 Capt, 5 Lt, 2 2Lt and 6 OCdt, for a total of 88 officers. It held 1 CWO (with 1 promotion to follow), 8/7 MWO, 37 WO, 75 Sgt, 35 MCpl, 37 Cpl and 2 Pte for a total of 195 other ranks and a grand total of 283 Regular Force Intelligence Branch personnel. The Reserve Force establishment for Intelligence Branch personnel was 24 officers and 50 NCOs. Regular Force Support Staff NCOs were included in the Regular Force figures.
[2] David Stafford, Editor; and Rhodri Jeffreys-Jones, Editor. American-British-Canadian Intelligence Relations, (Routledge; 1st Edition, 1 Sep 2000), introduction.
[3] Letter from Sir William S. Stephenson, CC, MC, DFC, forwarded to the Intelligence Branch Advisor, LCol V.V. Ashdown, for reading to attendees at the Intelligence Branch Inauguration Mess Dinner, CFB Borden, Ontario, 29 October 1982.
[4] Sinister Sam's Notebook, Edition 1, March 1997, pp. 8-10.
[5] Internet: http://people.howstuffworks.com/sept-eleven1.htm. 8 Oct 2003.
[6] Michael J. Cole, Smokescreen: Canadian Security Intelligence after September 11, 2001, (iUniverse, September 2008), introduction.
[7] Dwight Hamilton, Editor, Inside Canadian Intelligence: Exposing the New Realities of Espionage and International Terrorism. (Dundurn, 2nd Edition, 13 June 2011), introduction.
[8] David Last, Editor; and Bernd Horn, Editor, Choice of Force, Special Operations for Canada. (Special Operations Series #2, Queen's Policy Studies Series #41, 1 May 2005), introduction.
[9] LCol Victor V. Ashdown, Intelligence Branch Advisor, Letter to all Intelligence Branch Members, 17 Aug 1982.


text:
Q: Classes Issue in EMNIST Dataset So I'm using the dataset from here https://www.kaggle.com/crawford/emnist
namely emnist-letters-train-labels-idx1-ubyte.gz
When I go through it returns in 27 classes whilst there should only be 26 as it's for alphabets.
I dug in as much as I can but failed to find in labels for these.
Any help could be great.

A: A guess from my side would be they left one spare class if the sign is not a letter from the given alphabet or e.g. a number. So if the sign cannot be classified, the 27th spare class ("not a letter") will be assigned to it.
Did you already try to feed it some sign which is not a letter and see if it lands in the same class most of the time?


text:
Dr. Leah Cowen - How a Deadly Fungus Evades the Immune System
by Iliana Sztainbok
Discovery may shed light on new therapies for deadly bloodstream infections
Jim Oldfield (via U of T News)
Dr. Leah Cowen
The global burden of fungal superbugs is much greater in Africa than Europe or North America (photo of patients at camp for internally displaced persons by UNAMID via Flickr)
New research from the University of Toronto has scientists re-thinking how a lethal fungus grows and kills immune cells. The study hints at a new approach to therapy for Candida albicans, one of the most common causes of bloodstream infections.
Previously, scientists thought that Candida albicans spread by changing from a single, round cell to a long string of cells, or filaments. They thought this shape change allowed the fungus to move through the bloodstream and let its filaments penetrate tissues and destroy immune cells.
But the new study, published today in Nature Communications, shows that a little bit of sugar on the surface of fungal cells triggers the death of immune cells that would otherwise kill the fungus.
"It's not the shape-change per se that enables the fungus to kill the immune cell, but what happens along with it," says Professor Leah Cowen, lead researcher on the study who holds the Canada Research Chair in Microbial Genomics and Infectious Disease in U of T's department of molecular genetics. "The addition of glycosylated proteins, which are proteins with a sugar attached, re-models the surface of the fungal cells."
Cowen (pictured at right) and her lab found that Candida albicans can kill immune cells even after its cells have died. They let immune cells called macrophages consume the fungus, and after an hour they removed the fungal cells from the macrophages. Then they exposed new macrophages to fungal cells that had been consumed and those that had not, and they compared the results.
"The fungal cells that were never internalized by macrophages couldn't kill the fresh macrophages, but those that had been inside a macrophage could kill beautifully," says Cowen. That finding was a clue. The researchers reasoned that the change in the fungal cells that turned them into killers was probably on their surface, since dead cells have no active internal processes.
The researchers then used an enzyme called Endo H to snip off sugars on the glycosylated proteins attached to the dead fungal cells. The change completely blocked the ability of the fungus to kill – a strong lead on a new and needed therapeutic strategy for Candida albicans.
Globally, fungi kill more than 1.5 million people a year. In the U.S., Candida fungi account for almost 90 per cent of hospital-acquired fungal infections, and in Canada they're the third most common cause of bloodstream infections in intensive care units. More than 40 per cent of people with a systemic Candida albicans infection will die.
A therapy that targets the ability of fungal cells to outfox the immune system would be promising, says Cowen, because it might minimize effects on healthy microbes and avoid spurring drug resistance.
As well, some anti-fungals in development – including one in Cowen's lab – are hindered because the target proteins are present in both fungi and humans. That means a drug has to distinguish between the fungal and human versions of the target.
"If you develop a drug that targets something that's only found in fungi, it's less likely to have side effects in a human," says Cowen.
In her Nature Communications study, Cowen used a powerful Candida albicans mutant library, which the pharmaceutical company Merck recently made public. The library let Cowen and her team test the function of almost all genes in the Candida albicans genome, where before they could test just 10 per cent.
"It really let us approach this pathogen from a holistic perspective and evaluate the role of all its genes in disease," says Cowen.
The researchers used the library to do the first genome-scale analysis of the fungus's ability to change shape and grow, and they discovered more than 800 regulators of this process, which they published March 31, 2015 with their other findings.
"It's cool because we have a ton of new biology to explore, hundreds of possible drug targets and a new appreciation of how fungal pathogens interact with immune systems," says Cowen. "It's been a lot of fun."
Posted Monday, March 30, 2015


text:
Q: CAS - Logout not working properly My Java Web Application is called within a platform with an user already logged into CAS. This platform has a LOGOUT button.
When my application is reached for the first time in a session, the current user is correct. But if user clicks on LOGOUT and he signs in with a different account, when my app is reached again the current user is the first one.So, I think that logout isn't working properly.
My web.xml is the following:

<filter-name>CAS Single Sign Out Filter</filter-name>
<filter-class>org.jasig.cas.client.session.SingleSignOutFilter</filter-class>
</filter>
 <filter>
        <filter-name>CAS Authentication Filter</filter-name>
        <filter-class>org.jasig.cas.client.authentication.AuthenticationFilter</filter-class>
        <init-param>
            <param-name>casServerLoginUrl</param-name>
            <param-value>https://casServer/login</param-value>
        </init-param>
        <init-param>
            <param-name>serverName</param-name>
            <param-value>http://localhost:8082</param-value>
        </init-param>
    </filter>
    <filter-mapping>
        <filter-name>CAS Authentication Filter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>
    <filter>
        <filter-name>CAS Validation Filter</filter-name>
        <filter-class>org.jasig.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter</filter-class>

        <init-param>
            <param-name>casServerUrlPrefix</param-name>
            <param-value>https:/casServer/cas/</param-value>
        </init-param>
        <init-param>
            <param-name>serverName</param-name>
            <param-value>http://localhost:8082</param-value>
        </init-param>
    </filter>
    <filter-mapping>
        <filter-name>CAS Validation Filter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>
    <filter>
        <filter-name>CAS HttpServletRequest Wrapper Filter</filter-name>
        <filter-class>org.jasig.cas.client.util.HttpServletRequestWrapperFilter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>CAS HttpServletRequest Wrapper Filter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>
    <filter>
        <filter-name>CAS Assertion Thread Local Filter</filter-name>
        <filter-class>org.jasig.cas.client.util.AssertionThreadLocalFilter</filter-class>
    </filter>
 <filter-mapping>
<filter-name>CAS Single Sign Out Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<listener>
        <listener-class>org.jasig.cas.client.session.SingleSignOutHttpSessionListener</listener-class>
    </listener>

Can someone help me?


text:
About Our Surgery
PPG Minutes 4 October 2021
Back to Patient Participation Group
Minutes of the AGM meeting held on Monday 4th October 2021 at 19.00hrs
Present: Cec Smith (Chair), Alastair Knight (Vice Chair) Margaret Perrin (Secretary), Miriam Nicholls, Frank Soden. Tracy Doel, Jane Ingham. Charlotte Gorman. Guest Lisa Hepworth
Apologies, Denise Richards, Diane Vincent, Shayne Smith,
Minutes of the last meeting were agreed. Proposed: Alistair Knight Seconded: Frank Soden.
Matters arising from the previous meeting. Nil.
Cec Smith Chair welcomed everyone to the meeting and thanked them for attending, Cec informed the group of the sad passing of our colleague and friend Marion Burfield.
Lisa Hepworth who is the practice patient's Services Manager explained to the group that she holds a group session on a Wednesday afternoon from 2.00pm – 4.00pm for carers which is held at the surgery. Lisa offers several activities for them to take part in for example trips out, motivational speakers, art & craft, and various demonstrations. This is a drop-in session and help; guidance and advice are also available at these sessions. The public can refer someone, or anyone can self-refer if they think help is required.
A specific contact e mail address is being set up to enable people to contact Lisa directly, which will be published later. These sessions are proving to be a health benefit to those attending.
Surgery News:
Charlotte explained to the group that she had the car parking issue in hand and would report back to the group when she had any further information.
Charlotte highlighted the fact that some members of staff at the surgery had received anonymous hate mail from the public. This included the doctors and the practice management team. The reception staff are also dealing with abusive patients over the phone and in the surgery on a daily basis which is totally unacceptable behaviour. They are also dealing with patients who are refusing to wear masks in the surgery.
From Monday 4th October the 12 doctors are completing 4 extra consultations per day, 2 in the morning and 2 in the afternoon, this is only a temporary measure for the time being.
Patient Survey:
3 working groups have been set up on the back of the recent patient survey. They will be looking at the telephone system, apps, access, and availability of appointments and the online system. They will publish a report when compiled at the end of November.
Staffing: At present there are several job vacancies being advertised,
A GP, 2 Clinical Pharmacists, a Pharmacy technician, a First Contact Physiotherapist, and an Advance Nurse Practitioner. The surgery has recently recruited a receptionist, an apprentice and two Kick Start Receptionists (Trainees), and are interviewing for more reception staff.
Flu / Covid sessions:
The surgery hope to have all the care homes vaccinated by 1st November 2021.
Dates for Covid sessions at the surgery: 30th October 27th November 11th December.
Patients can also book an online appointment if they choose at one of the local vaccination centres if 180 days have passed since their last covid vaccination.
Other Issues:
A member of the group asked if someone had been taken ill whilst abroad how would they be able to access their medical records:
Charlotte explained that they could use the NHS app or e mail the surgery at info.ghs@nhs.net who would pass on the required information to the individual and clinicians.
Charlotte was asked by a member of the group if patients had to book a slot on the new Health Monitor which was provided by the League of Friends and is situated in the downstairs waiting room. She explained that anyone can use it at any time. When it is set up by the ICT team the information provided will be automatically recorded on your medical records, until then you will have to take the printout it provides now to reception, and they will record it for you.
A member of the committee asked if the surgery still offer ear syringing, Charlotte said they only carry out ear syringing if it proves to be a serious medical issue.
Some Opticians will carry out syringing but will charge a fee for the service.
Meeting closed at 7.55
Margaret Perrin
PPG Minutes 5 December 2022
PPG Sign Up
PPG Minutes 3 June 2019
PPG AGM Minutes 19 August 2019
PPG AGM Minutes 9 August 2021
PPG Minutes 7 February 2022
PPG Minutes 13 June 2022
Online Help Page
Update Your Clinical Records
Fees for Non-NHS Services
Park Run Practice
Focus Group Sign Up
National Opt Out of - Using your Health Data for Planning and Research
Admin Queries
Out of Hours Service
Accessing Our Online Services
Need to order a prescription?


Not everyone loses weight for the same reasons or the same way, so we will not treat your sessions as if you do. All of our sessions are individual and confidential. Your hypnosis session will be designed with your personal success in mind.
Hypnosis allows the changing of old programming that is causing you to eat out of habit, emotions and learned behaviors from your upbringing or past experiences.
Weight management hypnosis is geared to modify the thoughts influencing a person's eating and exercise habits. Rather than focusing on the loss of weight or pounds. The hypnotist assist you in learning to naturally focus on what you want and know why you want it. In other words discovering your deeper goals.
Many people set their goals as weight loss but what they are really wishing for is to look and feel better. In plain English they want to be happy and healthy.
By defining and helping establish the proper desire behind each goal, hypnotist consistently have been able to see their clients achieve astounding results in weight management.
If you have ever eaten as a response to emotional situations, you may begin to get an idea as to how powerful our methods for weight loss can be! Once old feelings from the past are neutralized and the new feelings are dealt with in a satisfying way, you will be on your way to not only losing your excess weight, but also keeping it off.
Our programs range from 2 to 6 sessions. We not only use hypnosis, but often teach you self hypnosis so that you can continue to reinforce your success forever. Our program also includes teaching you about the covert language of feelings (emotions). This is a powerful tool to assist you in responding to your feelings properly so that you can reduce or eliminate the emotional distress that keeps many people locked in self-destructive eating habits.
Even if you have tried diets or hypnosis before to address your weight issue, you will be surprised at how different and effective our programs are. Many other programs do not take into account factors such as family training, mood and emotions, habits, quality of diet, exercise level, genetic predisposition and other contributing factors.
Most weight loss programs are selling simplicity and for this reason they simply do not work.
Experience for Yourself....What others have achieved!


text:
using Should;
using Xunit;

namespace Nancy.Swagger.Tests
{
    public class SwaggerTypeMappingTests
    {
        [Fact]
        public void ShouldAdd_AndGet_TypeMappings()
        {
            SwaggerTypeMapping.ResetMappedTypes();

            Assert.False(SwaggerTypeMapping.IsMappedType(typeof(long)));

            SwaggerTypeMapping.AddTypeMapping(typeof(long), typeof(double));

            Assert.True(SwaggerTypeMapping.IsMappedType(typeof(long)));
            Assert.Equal(typeof(double), SwaggerTypeMapping.GetMappedType(typeof(long)));
        }

        [Fact]
        public void ShouldAdd_AndGet_NestedTypeMappings()
        {
            SwaggerTypeMapping.ResetMappedTypes();

            Assert.False(SwaggerTypeMapping.IsMappedType(typeof(long)));

            SwaggerTypeMapping.AddTypeMapping(typeof(int), typeof(long));
            SwaggerTypeMapping.AddTypeMapping(typeof(long), typeof(double));

            Assert.True(SwaggerTypeMapping.IsMappedType(typeof(int)));
            Assert.True(SwaggerTypeMapping.IsMappedType(typeof(long)));

            Assert.Equal(typeof(double), SwaggerTypeMapping.GetMappedType(typeof(int)));
        }
    }
}


You have any questions about Toyota Hilux Surf 3.4 2005? What's Toyota Hilux Surf 3.4 2005 fuel consumption in the city and on the highway ? What Fuel Should I Use in My Toyota Hilux Surf 3.4 2005? See a detailed table of specification of the vehicle on page this to website txautonet.com.


Raw Food Diet Benefits & Is Raw Food Really Better for You?
You are here: Home / Diet & Weight Loss / Raw Food Diet Benefits, Is Raw Food Really Better for You?
Raw Food Diet Benefits, Is Raw Food Really Better for You?
Raw foods carry very little calories, so taking more of these can do a great job in detoxifying the body and helping in weight loss. When people turn to a diet which is all-raw, weight loss is quickly realized. Raw foods are considered live because they contain enzymes such as lipase and protease, which are very crucial in weight loss. Lipase aids the body in digestion, burning fat and distributing fat through the body. Absence of lipase explains why fat accumulates in the body at times. Protease on the other and, will help your body in breaking down proteins and eliminating toxins. Elimination of toxins makes a direct contribution towards weight loss because under most circumstances, your body will tend to store the excess toxins in body fat.
Raw foods are associated with high fibre content. Fibre on the other hand, plenty in seeds, fruits and vegetables, plays a great role in the human body. For instance, it is a weight control measure but can also enhance cardiovascular health. Fibre also carries disease fighting phytochemicals and can enhance your digestive health.
You may not realize this until you try the diet out. Eating raw results in an extraordinary energy boost. The human body will normally distribute energy towards muscles and organs, cleansing, fat loss and waste elimination, digestion (which takes up most energy) and finally towards crucial functions such as respiration and blood circulation.
The body rarely gets enough energy to complete all these tasks because they are competing to get the most energy from the same source. Taking more and more of the raw foods therefore has the implication of huge energy bursts because there is a decreased need for energy to digest the food. This also means more stamina; thus one can engage in any physical activity of their choice without feeling depleted so fast.
Human beings are basically what they eat. This is indicative that the food we consume will not only affect our physical nature but also the emotions, perceptions, dreams and ideas. Raw food has all the essential nutrients needed for the nourishment of your brain. When all these are provided, memory stays sharp besides an improved concentration. Alertness also translates to a mental stamina that will allow you to complete whatever tasks that require the commitment of your brain.
Looking at highly processed and excessively cooked foods; they contain a number of chemicals which are associated with mild or even extreme degrees of stress. This pollutes human consciousness and storms our emotions. One will therefore barely function as expected in such a state. This is why raw foods play a vital role in boosting emotional balance.
The role that a raw diet plays towards the overall look of your skin cannot be downplayed. A number of people, especially women, will experience reduced puffiness on their skin once they take raw foods in plenty. There is a series of beauty gains which come along with these foods. For example, nails will be stronger, hair will look shinier and the eyes too will appear brighter.
Many people ignore the fact that the appearance of the skin depends more on what they take in rather than what they apply on it. Nourishment starts internally before it spreads to the outwardly visible parts of the body. The moment you reduce consumption of junk and pay attention to unprocessed fruits, vegetables and seeds, the skin will grow softer, finer and more firm.
To improve your cooking skills its often good to attend a cooking class that specialises in raw foods cooking.
Most of the raw foods have an abundance of antioxidants, Vitamin A and vitamin C. These ingredients boost your immunity and may significantly reduce the threat of serious infections such as high blood pressure, diabetes, cancer and heart problems. Talking of broccoli for instance, it has cancer fighting properties only when it is taken raw. If broccoli is cooked beyond the recommended temperatures, however, it loses these essential properties and regardless of how frequently it is consumed, cancer may be knocking so fast.
Raw foods are known for their high water content, a reason why they easily cool, and hydrate the body. When a person snacks on fresh vegetables and fruits like watermelons pears, cucumbers and leafy greens, they stay energized and hydrated especially during the hot season.
Proper hydration also translates to better digestion because a lot of water goes into the process of braking food down. Toxins will as well get flushed out of the body easily when there is adequate hydration. In essence, therefore, keeping the body hydrated with the help of these foods improves general body health.
In summary, considering the health benefits that one gets out of raw foods, indeed they deserve all the glory. Rather than grappling with lifestyle illnesses, therefore, it is time that you turned to an easier preventive measure which does not in any way leave you starved.


text:
Almatech was responsible for the complete design, development and delivery of the 3 models of the SPICE Slit-Change Mechanism.
In order to guaranty optical cleanliness level (PAC<30ppm) while fulfilling stringent positioning accuracies (±10 μm / 200 arcsec) and repeatability (±3 μm) requirements for slit positioning in the optical path of the instrument, a linear guiding system based on a double flexible blade arrangement has been selected. The concept of the mechanism is compliant (wear-free), compatible with cryogenic conditions with an integrated calibration system and does not require a launch-lock system. All requirements including cyclability (over 54'000 cycles) have been fulfilled.
"The Slit-Change Mechanism is a perfect example of all the benefits compliant mechanisms can bring in terms of reliability and absence of contamination. I am convinced that this type of design is the future!"
Gabriel Paciotti
Solar Orbiter is a Science mission of jointly developed between ESA and NASA, that was selected as the first medium (M)-class mission of ESA's Cosmic Vision programme for launch in 2019. Solar Orbiter's goal is to address the central question of Heliophysics: how does the Sun create and control the heliosphere? Solar Orbiter is designed to identify the origins and causes of the solar wind, the heliospheric magnetic field, the solar energetic particles, the transient interplanetary disturbances, and the Sun's magnetic field.
About the payload
SPICE is one of 10 instruments on board Solar Orbiter. It is a high resolution imaging spectrometer operating at extreme ultraviolet wavelengths. SPICE will address the key science goals of the Solar Orbiter mission, by providing the quantitative knowledge of the physical state and composition of the plasmas in the solar atmosphere, in particular investigating the source regions of outflows and ejection processes which link the solar surface and corona to the heliosphere. SPICE is designed to study the structure, dynamics and composition of the transition region and corona by observing key emission lines on the solar disk on timescales from seconds to tens of minutes.
The Solar Orbiter mission (Credit ESA)
slit carrier positionning accuracy
slit carrier position repeatability
Paciotti G., Humphries M., Rottmeier F., Blecha L., Development and preliminary testing of a high precision long stroke Slit Change Mechanism for the SPICE instrument
presented at the 42nd Aerospace Mechanisms Symposium, NASA Goddard Space Flight Center, May 2014
Khanenya N., Paciotti G., Forzani E., Blecha L., Development and Testing of a High-Precision Position and Attitude Measuring System for a Space Mechanism
presented at the 43rd Aerospace Mechanisms Symposium, NASA Ames Research Center, May 4-6, 2016


Finally some milder weather; wahoo! On Friday it was a balmy 9 degrees at rosybee so we took the opportunity to have a quick peek at the bees; only taking the roof off to see as far as ekes we have put above the queen excluder as a space for extra food. It all good news: all four hive have made it through the winter although with differing levels of activity.
All but one had been eating the fondant (see above) we gave them at Christmas and one hive had completely finished their block so we gave them a bit more. There were not many bees flying but we did see a couple of bees carrying bright orange pollen (see picture left) into the hives which is a sure sign that their queen has started laying and they need the pollen to feed the babies.
The one hive that had not touched its fondant probably has plenty of honey as the hive still has some weight to it. However this may mean that their numbers are greatly reduced, hence why they have not consumed so much, therefore we will keep an eye on then just case.