The best way to fix these problems is to change the original medm file such that the automated conversion to BOY files is better. Usually the problem is that the medm field width is not sized to the actual text size, etc. This way when the medm file is updated in the future with new widgets, etc. the automatic conversion can produce new usable OPI files. I see too many cases where people are using BOY or EDM files that don't expose more recent areaDetector features because they did a manual edit of an older version.
________________________________
From: [email protected] [[email protected]] on behalf of Phil Atkin [[email protected]]
Sent: Thursday, February 04, 2016 6:17 AM
To: [email protected] list
Subject: BOY formatting of uniqueID and timestamp
Hi,
The areaDetector-supplied opi files NDStdArrays and NDPluginBase don't make a good job of formatting these values:
[cid:[email protected]]
I expect that they were translated from the original .adl files using an automated tool. What formatting etc. settings would be suitable for these values?
Regards
Phil
--
[cid:[email protected]]Pixel Analytics is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP
- References:
- BOY formatting of uniqueID and timestamp Phil Atkin
- Navigate by Date:
- Prev:
BOY formatting of uniqueID and timestamp Phil Atkin
- Next:
Re: BOY formatting of uniqueID and timestamp Hinxx
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
BOY formatting of uniqueID and timestamp Phil Atkin
- Next:
Re: BOY formatting of uniqueID and timestamp Hinxx
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|