Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This seems to work, others may have better ideas:</p> <pre><code>#include &lt;ostream&gt; #include &lt;thrust/host_vector.h&gt; #include &lt;thrust/device_vector.h&gt; #include &lt;thrust/transform.h&gt; #include &lt;thrust/functional.h&gt; #include &lt;thrust/copy.h&gt; #include &lt;thrust/fill.h&gt; #define DSIZE 10 template &lt;typename T&gt; thrust::device_vector&lt;T&gt; operator+(thrust::device_vector&lt;T&gt; &amp;lhs, const thrust::device_vector&lt;T&gt; &amp;rhs) { thrust::transform(rhs.begin(), rhs.end(), lhs.begin(), lhs.begin(), thrust::plus&lt;T&gt;()); return lhs; } template &lt;typename T&gt; thrust::host_vector&lt;T&gt; operator+(thrust::host_vector&lt;T&gt; &amp;lhs, const thrust::host_vector&lt;T&gt; &amp;rhs) { thrust::transform(rhs.begin(), rhs.end(), lhs.begin(), lhs.begin(), thrust::plus&lt;T&gt;()); return lhs; } int main() { thrust::device_vector&lt;float&gt; dvec(DSIZE); thrust::device_vector&lt;float&gt; otherdvec(DSIZE); thrust::fill(dvec.begin(), dvec.end(), 1.0f); thrust::fill(otherdvec.begin(), otherdvec.end(), 2.0f); thrust::host_vector&lt;float&gt; hresult1 = dvec + otherdvec; std::cout &lt;&lt; "result 1: "; thrust::copy(hresult1.begin(), hresult1.end(), std::ostream_iterator&lt;float&gt;(std::cout, " ")); std::cout &lt;&lt; std::endl; thrust::host_vector&lt;float&gt; hvec(DSIZE); thrust::fill(hvec.begin(), hvec.end(), 5.0f); thrust::host_vector&lt;float&gt; hresult2 = hvec + hresult1; std::cout &lt;&lt; "result 2: "; thrust::copy(hresult2.begin(), hresult2.end(), std::ostream_iterator&lt;float&gt;(std::cout, " ")); std::cout &lt;&lt; std::endl; // this line would produce a compile error: // thrust::host_vector&lt;float&gt; hresult3 = dvec + hvec; return 0; } </code></pre> <p>Note that in either case, I can specify a host or device vector for the result, since thrust will see the difference and automatically generate the necessary copy operation. So the result vector type (host, device) in my templates is not critical.</p> <p>Also note that the <code>thrust::transform</code> function parameters you had in your template definition weren't quite right.</p>
    singulars
    1. This table or related slice is empty.
    1. POOverloading "+" operator for Thrust, any ideas?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRobert Crovella
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POOverloading "+" operator for Thrust, any ideas?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAh, I think that will work. I'll check it when I get back to work in the morning.
      singulars
      1. PO
      1. USTyler Jandreau
    2. COI guess one other thing I should have pointed out is that (I think) you were suggesting an in-place tranform (which is why you proposed returning `lhs`, and I followed your convention), but the effect of that is one of the two operands (lhs) is getting overwritten. So this might create the slightly non-intuitive behavior that `result = vec1 + vec2;` puts the answer in *both* `result` and `vec1`.
      singulars
      1. PO
      1. USRobert Crovella
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload