I've encountered what appears to be a bug when exporting desktops:
It seems that when I export an IADS desktop, all derived parameters
that are used in ANY desktop in the config file get exported along
with the Analysis windows. My understanding of how this is supposed
to work is that only the derived parameters needed to recreate the
particular desktop that's being exported are supposed to be included
in the export.
Instead, I'm getting every derived parameter from every desktop. This
is a problem, because when multiple users export and the re-import
desktops after making changes to pre-existing derived parameters,
those changes are overwritten by the other users' desktops. For
instance:
Person A edits parameter A, then imports his desktop to the master
config file.
Person B does not edit parameter A, but has parameter A included in
his exported desktop even though he doesn't use it. When Person B
imports his desktop, it overwrites Person A's parameter A.
On Jun 29, 5:28 am, Eric Fallabel <falla...@gmail.com> wrote:
> I've encountered what appears to be a bug when exporting desktops:
> It seems that when I export an IADS desktop, all derived parameters
> that are used in ANY desktop in the config file get exported along
> with the Analysis windows. My understanding of how this is supposed
> to work is that only the derived parameters needed to recreate the
> particular desktop that's being exported are supposed to be included
> in the export.
Your understanding is correct. It should only export the parameters
necessary to recreate your desktop.
> Instead, I'm getting every derived parameter from every desktop. This
> is a problem, because when multiple users export and the re-import
> desktops after making changes to pre-existing derived parameters,
> those changes are overwritten by the other users' desktops. For
> instance:
> Person A edits parameter A, then imports his desktop to the master
> config file.
> Person B does not edit parameter A, but has parameter A included in
> his exported desktop even though he doesn't use it. When Person B
> imports his desktop, it overwrites Person A's parameter A.
Yes, that would definitely be a problem. I'm going to test this out
myself right now.
Can you tell me what version of IADS you are running?
Also, can you run a Desktop Summary on your desktop and see if those
same parameters show up in that list?
> On Jun 29, 5:28 am, Eric Fallabel <falla...@gmail.com> wrote:
> > I've encountered what appears to be a bug when exporting desktops:
> > It seems that when I export an IADS desktop, all derived parameters
> > that are used in ANY desktop in the config file get exported along
> > with the Analysis windows. My understanding of how this is supposed
> > to work is that only the derived parameters needed to recreate the
> > particular desktop that's being exported are supposed to be included
> > in the export.
> Your understanding is correct. It should only export the parameters
> necessary to recreate your desktop.
> > Instead, I'm getting every derived parameter from every desktop. This
> > is a problem, because when multiple users export and the re-import
> > desktops after making changes to pre-existing derived parameters,
> > those changes are overwritten by the other users' desktops. For
> > instance:
> > Person A edits parameter A, then imports his desktop to the master
> > config file.
> > Person B does not edit parameter A, but has parameter A included in
> > his exported desktop even though he doesn't use it. When Person B
> > imports his desktop, it overwrites Person A's parameter A.
> Yes, that would definitely be a problem. I'm going to test this out
> myself right now.
> Can you tell me what version of IADS you are running?
> Also, can you run a Desktop Summary on your desktop and see if those
> same parameters show up in that list?
On Jun 29, 9:14 am, Eric Fallabel <falla...@gmail.com> wrote:
> Version 6.3 is what I'm running.
Thanks.
> I'm not sure how to run a Desktop Summary, but I'll do it as soon as I
> figure that out.
If you open up the Configuration Tool, under the 'Tools' menu there is
an option for the Desktop Summary Report. When you run it after
selecting your desktop, it will open up a table showing you all the
windows, displays and parameters on your desktop. You can sort on the
parameter name and look for any derived parameters that you think
don't belong on your desktop. Let me know what you find.
> On Jun 29, 11:29 am, Brenda Rassmussen <bre...@iads-soft.com> wrote:
> > Hi Eric,
> > On Jun 29, 5:28 am, Eric Fallabel <falla...@gmail.com> wrote:
> > > I've encountered what appears to be a bug when exporting desktops:
> > > It seems that when I export an IADS desktop, all derived parameters
> > > that are used in ANY desktop in the config file get exported along
> > > with the Analysis windows. My understanding of how this is supposed
> > > to work is that only the derived parameters needed to recreate the
> > > particular desktop that's being exported are supposed to be included
> > > in the export.
> > Your understanding is correct. It should only export the parameters
> > necessary to recreate your desktop.
> > > Instead, I'm getting every derived parameter from every desktop. This
> > > is a problem, because when multiple users export and the re-import
> > > desktops after making changes to pre-existing derived parameters,
> > > those changes are overwritten by the other users' desktops. For
> > > instance:
> > > Person A edits parameter A, then imports his desktop to the master
> > > config file.
> > > Person B does not edit parameter A, but has parameter A included in
> > > his exported desktop even though he doesn't use it. When Person B
> > > imports his desktop, it overwrites Person A's parameter A.
> > Yes, that would definitely be a problem. I'm going to test this out
> > myself right now.
> > Can you tell me what version of IADS you are running?
> > Also, can you run a Desktop Summary on your desktop and see if those
> > same parameters show up in that list?
It turns out that I may have been fooling myself with what parameters
were being brought along. Another user had some misleading Subgroup
names that led me to believe his parameters were not needed for a
particular display, when they were in fact needed to create it. From
what I can see the Export works as advertised.
However, I've still had the problem on many occasions where a derived
parameter has been overwritten with an old version of an equation.
Here's a typical example:
After a flight I update my Desktop. I add a few new stripcharts or
ActiveX controls, add a couple of derived parameters and change the
equation of a derived parameter that already existed prior to the
flight.
When I go to telemetry after exporting my updated desktop, I see the
new stripcharts and ActiveX controls, I see the new derived
parameters, but the equation for the older derived parameter appears
to have not been updated. I'd be willing to chalk this up to some
user error, but it's happened many times. I thought that my previous
theory of an Export bug would have explained it, but that's been
proved wrong.
On Jun 29, 12:44 pm, Brenda Rassmussen <bre...@iads-soft.com> wrote:
> On Jun 29, 9:14 am, Eric Fallabel <falla...@gmail.com> wrote:> Version 6.3 is what I'm running.
> Thanks.
> > I'm not sure how to run a Desktop Summary, but I'll do it as soon as I
> > figure that out.
> If you open up the Configuration Tool, under the 'Tools' menu there is
> an option for the Desktop Summary Report. When you run it after
> selecting your desktop, it will open up a table showing you all the
> windows, displays and parameters on your desktop. You can sort on the
> parameter name and look for any derived parameters that you think
> don't belong on your desktop. Let me know what you find.
> Brenda
> > -Eric
> > On Jun 29, 11:29 am, Brenda Rassmussen <bre...@iads-soft.com> wrote:
> > > Hi Eric,
> > > On Jun 29, 5:28 am, Eric Fallabel <falla...@gmail.com> wrote:
> > > > I've encountered what appears to be a bug when exporting desktops:
> > > > It seems that when I export an IADS desktop, all derived parameters
> > > > that are used in ANY desktop in the config file get exported along
> > > > with the Analysis windows. My understanding of how this is supposed
> > > > to work is that only the derived parameters needed to recreate the
> > > > particular desktop that's being exported are supposed to be included
> > > > in the export.
> > > Your understanding is correct. It should only export the parameters
> > > necessary to recreate your desktop.
> > > > Instead, I'm getting every derived parameter from every desktop. This
> > > > is a problem, because when multiple users export and the re-import
> > > > desktops after making changes to pre-existing derived parameters,
> > > > those changes are overwritten by the other users' desktops. For
> > > > instance:
> > > > Person A edits parameter A, then imports his desktop to the master
> > > > config file.
> > > > Person B does not edit parameter A, but has parameter A included in
> > > > his exported desktop even though he doesn't use it. When Person B
> > > > imports his desktop, it overwrites Person A's parameter A.
> > > Yes, that would definitely be a problem. I'm going to test this out
> > > myself right now.
> > > Can you tell me what version of IADS you are running?
> > > Also, can you run a Desktop Summary on your desktop and see if those
> > > same parameters show up in that list?
>It turns out that I may have been fooling myself with what parameters >were being brought along. Another user had some misleading Subgroup >names that led me to believe his parameters were not needed for a >particular display, when they were in fact needed to create it. From >what I can see the Export works as advertised.
Ok, good...
>When I go to telemetry after exporting my updated desktop, I see the >new stripcharts and ActiveX controls, I see the new derived >parameters, but the equation for the older derived parameter appears >to have not been updated. I'd be willing to chalk this up to some >user error, but it's happened many times. I thought that my previous >theory of an Export bug would have explained it, but that's been >proved wrong.
Yes, it's a little confusing, but the basic rule for parameter updates is: If the parameter doesn't exists in the PD table, then add it. If it already exists, don't modify it.
|
