Hi Jabir,

I think your approach for accessing storage registers is good and efficient. 
The scratch space matrices we allocate are used for temporary storage, and gets 
overwritten whenever we need to utilize that storage for some other temporary 
data. But you can of course allocate a new matrix, and copy any matrix of 
matching size into the new storage any time. You just need to be careful about 
where to place copy operation. It should be right after when a scratch space 
matrix gets written the data you actually need.

Best,
Semih

________________________________
From: [email protected] <[email protected]> on 
behalf of Jabir <[email protected]>
Sent: 04 March 2020 14:44
To: PyFR Mailing List <[email protected]>
Subject: [pyfrmailinglist] Storing and Accessing Data from Old Solutions


This email from [email protected] originates from outside Imperial. Do not 
click on links and attachments unless you recognise the sender. If you trust 
the sender, add them to your safe senders 
list<https://spam.ic.ac.uk/SpamConsole/Senders.aspx> to disable email stamping 
for this address.



Dear PyFR developers,

I am trying to access data from multiple storage registers (time levels) in the 
solver's point-wise kernels.
For scal_upts, I currently pass the id of a register of interest to the 
system.rhs() method, then use that id to set the active matrix of a 
"scal_upts_old" bank, which I declared in base/elements in the same way as 
scal_upts_inb/outb.
Is this the best approach in this case or is there a more 
straightforward/efficient way of passing this data to point-wise kernels?

How would I go about storing/accessing non-scal_upts data from older solutions, 
such as vect_upts and scal_fpts?  Is there a way to use a "scratch buf" for 
that?

I would really appreciate your help with this.

Thanks,

Jabir

--
You received this message because you are subscribed to the Google Groups "PyFR 
Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/pyfrmailinglist/cee13f85-2677-4a62-a317-9aa795d8fed0%40googlegroups.com<https://groups.google.com/d/msgid/pyfrmailinglist/cee13f85-2677-4a62-a317-9aa795d8fed0%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups "PyFR 
Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/pyfrmailinglist/AM6PR06MB550924541B18ABFE10D010C4A7E50%40AM6PR06MB5509.eurprd06.prod.outlook.com.

Reply via email to