Hi Hugh (&all)!
Jana is correct: I could probably do this without using the batch agenda; I
> do not think I am doing anything which fundamentally prevents this. But I
> could not work out how to do that either 🙁 . I will probably try to sort
> that out at some point.
>
It's actually very simple:
point.
Meanwhile, Oliver's hints have enabled me to get it working by using the batch
agenda.
Best wishes,
Hugh
From: Jana Mendrok
Sent: 18 July 2019 13:59
To: PUMPHREY Hugh
Cc: arts_users.mi@lists.uni-hamburg.de
Subject: Re: [arts-users] Extract element
Hi Hugh,
you are probably doing things in the batch agenda, that make you require or
prefer a batch agenda. But if it's just about multiple LOS - they can also
be done in a single, non-batch run (that's why sensor_los is a matrix; one
of it's dimensions is the number of LOS, or in a more general w
Hi Hugh,
Since ARTS is strongly typed, a Numeric cannot be assigned directly to a Matrix.
But you can extract it into a temporary variable and then use MatrixSetConstant:
Arts2 {
VectorCreate(my_loses)
VectorSet(my_loses, [180,170,160,150,140,130])
Print(my_loses)
IndexSet(ybatch_start, 0)
Inde
Dear ARTS gurus,
I am trying to use ARTS's batch feature to do calculations for a range of
values of sensor_los.
The relevant bit of my control file goes:
VectorCreate(my_loses)
VectorSet(my_loses, [180,170,160,150,140,130])
Print(my_loses)
IndexSet(ybatch_n,7)
AgendaSet(ybatch_calc_agenda){