<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress.com" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>subset &amp;laquo; WordPress.com Tag Feed</title>
	<link>http://wordpress.com/tag/subset/</link>
	<description>Feed of posts on WordPress.com tagged "subset"</description>
	<pubDate>Sat, 26 Jul 2008 08:53:05 +0000</pubDate>

	<generator>http://wordpress.com/tags/</generator>
	<language>en</language>

<item>
<title><![CDATA[Recorte Irregular no ERDAS 9.1]]></title>
<link>http://geotecnologias.wordpress.com/?p=59</link>
<pubDate>Fri, 02 May 2008 15:37:42 +0000</pubDate>
<dc:creator>sadeckgeo</dc:creator>
<guid>http://geotecnologias.wordpress.com/?p=59</guid>
<description><![CDATA[
Depois de termos apresentado um tutorial sobre recorte regular no ERDAS 9.1, muitas perguntas chega]]></description>
<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-25" src="http://geotecnologias.wordpress.com/files/2008/03/tutorial-erdas.jpg" alt="" width="510" height="58" /></p>
<p class="MsoNormal" style="text-align:justify;line-height:150%;">Depois de termos apresentado um tutorial sobre recorte regular no ERDAS 9.1, muitas perguntas chegaram sobre recorte irregular ou com limites de municípios ou áreas especiais. Apesar de já termos feito alguns tutoriais de outros softwares com essa temática, alguns técnicos só dispõem de licenças para outros softwares, por isso, vamos agora ao <strong>recorte irregular</strong> no ERDAS 9.1.</p>
<p class="MsoNormal" style="text-align:center;line-height:150%;"><a href="http://www.4shared.com/file/46168220/67a01b3/Recorte_Irregular_-_ERDAS_91.html" target="_blank"><img class="alignnone size-full wp-image-35 aligncenter" style="border:0;" src="http://geotecnologias.wordpress.com/files/2008/04/download_sadeck.png" alt="" width="175" height="75" /></a></p>
<p class="MsoNormal" style="text-align:justify;line-height:150%;">Bom trabalho!!!!!</p>
<p>Até a próxima.</p>
<p>Por: Luis Sadeck</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Recorte Regular - ERDAS 9.1]]></title>
<link>http://geotecnologias.wordpress.com/?p=47</link>
<pubDate>Sun, 27 Apr 2008 20:32:20 +0000</pubDate>
<dc:creator>sadeckgeo</dc:creator>
<guid>http://geotecnologias.wordpress.com/?p=47</guid>
<description><![CDATA[
Olá a todos, hoje vamos demonstrar como se faz o processo de recorte regular no Software ERDAS 9.1]]></description>
<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-25" src="http://geotecnologias.wordpress.com/files/2008/03/tutorial-erdas.jpg" alt="" width="510" height="58" /></p>
<p align="justify">Olá a todos, hoje vamos demonstrar como se faz o processo de recorte regular no Software ERDAS 9.1. Esse processo é bastante usado quando nossa área de trabalho não abrange a(s) imagem(s) toda(s) e precisamos retirar uma parte da informação que, nesse caso é desnecessária.</p>
<p align="justify">Optamos hoje pelo recorte regular, pensando na criação do Layout da carta imagem depois, ou seja, com o recorte regular você terá uma apresentação visual bem melhor.</p>
<p align="justify">Então vamos ao que importa.</p>
<p style="text-align:center;" align="justify"><a title="Download" href="http://www.4shared.com/file/45589527/30a4031a/Recorte_Regular_-_ERDAS_91.html" target="_blank"><img class="alignnone size-medium wp-image-35 aligncenter" style="border:0;" src="http://geotecnologias.wordpress.com/files/2008/04/download_sadeck.png?w=175" alt="" width="175" height="75" /></a></p>
<p style="text-align:left;">Um abraço a todos e até a próxima.</p>
<p style="text-align:left;">Por: Luis Sadeck</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Fibromyalgia and CIDP]]></title>
<link>http://linzworld.wordpress.com/?p=157</link>
<pubDate>Fri, 08 Feb 2008 08:15:48 +0000</pubDate>
<dc:creator>linzworld</dc:creator>
<guid>http://linzworld.wordpress.com/?p=157</guid>
<description><![CDATA[A study published in the February edition of the Oxford journal Rheumatology has found that a signif]]></description>
<content:encoded><![CDATA[<p class="abstract"><a href="http://www.ncbi.nlm.nih.gov/pubmed/18208823?dopt=AbstractPlus">A study published in the February edition of the Oxford journal <em>Rheumatology</em> </a>has found that a significant subset of Fibromyalgia patients show findings suggestive of chronic inflammatory demyelinating polyneuropathy (CIDP).</p>
<p class="abstract">The researchers said in their article that the "aetiopathogenesis [cause(s) and mechanisms] of... fibromyalgia ...(FMS) remains unknown", but recent reports "suggest that a subgroup of FMS subjects has an immune-mediated disease". The researchers primary objective was to study FMS subjects for evidence of an immune-mediated demyelinating polyneuropathy and their secondary objective was to determine the effects of treating these FMS subjects with the immune modulator, intravenous immunoglobulin (IVIg), which is used to treat CIDP. I'm not sure which "recent reports" they are referring to, but I wonder whether part of that was the South Korean study, published last year, that found some FMS patients have demyelinated nerve cells in the skin.</p>
<p class="abstract">Fifty-eight FMS subjects, 26 rheumatic non-FMS subjects and 52 non-rheumatic non-FMS subjects were studied. Subjective measures of paraesthesias (numbness/pins-and-needles), weakness, stocking hypaesthesia (decrease in sensitivity of the feet), pain, fatigue and stiffness were made. Objective measures of tenderness, proximal muscle strength and electrodiagnostic (EDX) evidence of polyneuropathy and demyelination were also made. Eleven other FMS subjects underwent sural nerve biopsy.</p>
<p class="abstract">The researchers found that paraesthesias, subjective weakness and stocking hypaesthesia were more common in FMS than in rheumatic patients without FMS. Proximal muscle strength was less in FMS than in rheumatic patients without FMS. EDX demonstrated a distal demyelinating polyneuropathy, suggestive of chronic inflammatory demyelinating polyneuropathy (CIDP), in 33% of FMS subjects. No rheumatic patients without FMS had polyneuropathy, or demyelination. Fifteen FMS/CIDP subjects were subsequently treated with IVIg and pain, tenderness and strength improved significantly. Fatigue and stiffness trended towards improvement.</p>
<p class="abstract">The researchers concluded that</p>
<blockquote>
<p class="abstract">"A significant subset of FMS subjects have clinical and EDX findings suggestive of CIDP. IVIg treatment shows promise in treating this subset. These observations have implications for better understanding and treating some FMS patients."</p>
</blockquote>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Jave Code : generate all possible subsets]]></title>
<link>http://laroutedeldorado.wordpress.com/?p=11</link>
<pubDate>Wed, 06 Feb 2008 06:58:27 +0000</pubDate>
<dc:creator>krackjack365</dc:creator>
<guid>http://laroutedeldorado.wordpress.com/?p=11</guid>
<description><![CDATA[import java.util.*;

/**
 * Illustrate subset generation via recursion
 * and by counting in binary ]]></description>
<content:encoded><![CDATA[<pre>import <b>java</b>.util.*;

/**
 * Illustrate subset generation via recursion
 * and by counting in binary and masking/shifting.
 * Neither method is demonstrably superior to the others.
 * &#60;P&#62;
 * Also shows abstract classes, use of inheritance to
 * process subsets, and timing in <b>Java</b>
 * &#60;P&#62;
 * @author Owen Astrachan
 *
 */

public class <b>SubsetStuff</b>
{
    /**
     * Class to process one subset. In general, subset generators
     * will call startAll, generate all subsets, then call finishAll.
     * The doOne method will be called for each element in some
     * subset, the finishOne method should be called after finishing
     * all elements in some subset.
     *
     */
    static abstract class OneSubsetProcessor{
	double myTime;

	public void startAll(){
	    myTime = System.currentTimeMillis();
	}

	public void finishAll(){
	    myTime = System.currentTimeMillis() - myTime;
	}
	public double getTime(){
	    return myTime/1000;
	}

	/**
	 * Called by subset generator with each element
	 * in one subset. To process a complete subset,
	 * methods doOne() and finishOne() should work
	 * together, e.g., finishOne() called after processing
	 * all elements.
	 */
	public abstract void doOne(Object o);
	public abstract void finishOne();

    }

    /**
     * Generate all subsets, the list of elements from
     * which subsets are generated is set via setList
     * or at construction time.
     * Each different generator will generate all subsets
     * via the method &#60;code&#62;process&#60;/code&#62; and process subsets
     * by that methods processor parameter.
     */

    static abstract class SubsetGenerator{
	List myList;

	public SubsetGenerator(List list){
	    myList = list;
	}

	public void setList(List list){
	    myList = list;
	}

	public abstract void process(OneSubsetProcessor thing);
    }

    /**
     * Generate all subsets recursively.
     */
    static class RecursiveSubsetGenerator extends SubsetGenerator {

	OneSubsetProcessor myThing;
	public RecursiveSubsetGenerator(List list){
	    super(list);
	}

	public void process(OneSubsetProcessor thing){
	    myThing = thing;
	    ArrayList list = new ArrayList();
	    myThing.startAll();
	    doGenerate(list,0);
	    myThing.finishAll();
	}

	protected void doGenerate(ArrayList list, int index){
	    if (index &#62;= myList.size()){
		for(int k=0; k &#60; list.size(); k++){
		    myThing.doOne(list.get(k));
		}
		myThing.finishOne();
	    }
	    else {
		list.add(myList.get(index));
		doGenerate(list,index+1);
		list.remove(list.size()-1);
		doGenerate(list, index+1);
	    }
	}
    }

    /**
     * Generate all subsets via bit patterns.
     */
    static class BitSubsetGenerator extends SubsetGenerator {

	OneSubsetProcessor myThing;

	public BitSubsetGenerator(List list){
	    super(list);
	}

	public void process(OneSubsetProcessor thing){
	    myThing = thing;
	    int size = 1 &#60;&#60; myList.size();
	    myThing.startAll();
	    for(int k=0; k &#60; size; k++){
		doProcess(k);
	    }
	    myThing.finishAll();
	}

	protected void doProcess(int bits){
	    int size = myList.size();
	    for(int k=0; k &#60; size; k++){
		if ( (bits &#38; 1) == 1){
		    myThing.doOne(myList.get(k));
		}
		bits = bits &#62;&#62; 1;
	    }
	    myThing.finishOne();
	}
    }

    /**
     * Counts subsets, note that doOne() does nothing.
     */
    static class Counter extends OneSubsetProcessor{
	int myCount;
	public Counter(){
	    myCount = 0;
	}
	public void startAll(){
	    super.startAll();
	    myCount = 0;
	}
	public void doOne(Object o){

	}
	public void finishOne(){
	    myCount++;
	}
    }

    /**
     * Prints subsets.
     */
    static class Printer extends OneSubsetProcessor{
	public void doOne(Object o){
	    System.out.print(o+" ");
	}
	public void finishOne(){
	    System.out.println();
	}
    }

    public static void main(String[] args){

	String[] array = {
	    "ant", "cat", "dog", "penguin", "lemur",
//	    "lion", "horse", "giraffe", "goat", "monkey",
//	    "zebra", "yak", "cougar", "tapir", "mongoose",
//	    "tiger", "kangaroo", "leopard", "cheetah", "ostrich",
//	    "antelope", "narwhal", "unicorn"
	};
	List list = Arrays.asList(array);
	SubsetGenerator sgr = new RecursiveSubsetGenerator(list);
	SubsetGenerator sgb = new BitSubsetGenerator(list);
	OneSubsetProcessor st = new Printer();
	Counter ct = new Counter();

	sgr.process(ct);
	sgb.process(st);
	System.out.println("count = " + ct.myCount);
	System.out.println("time = "+ct.getTime());
    } 

}</pre>
<p>Hail Steve !!</p>
<p>http://stefan-pochmann.info/spots/</p>
<p>http://www.cs.duke.edu/courses/fall04/cps100/code/sorting/SubsetStuff.java</p>
]]></content:encoded>
</item>

</channel>
</rss>
