The case files that are created to communicate data from a client to a PRO solver session and back, now use a different internal string character set. Especially for configurations where the session runs on a Linux machine, this greatly improves the time that is needed to read these cases.
The WebUI Table widget has been extended with the possibility to download the Table data to an Excel file. It is also possible to upload data from an Excel file to a WebUI Table. This is currently released as an Experimental Feature.
The Machine Time Has Been Changed Tolerance Data Download
The code to read and write case files has been completely re-written. This should not have any negative impact on existing models. The format of the case files has not been changed and thus is still compatible with older AIMMS versions. The new code fixes a few problems related to the order in which data was read in and the in between evaluation of definitions. If you encounter any problems because of this change, please let us know as soon as possible. For more details, see here.
The settings cog-wheel for several smaller widgets (such as button, label, upload, download and selection box) has been changed, such that it no longer floats outside the widget but stays inside so users can actually find it easily and have no overlap or out of viewport issues.
Knitro 11.1 has been added. Knitro 11.1 is only available for 64-bit Windows (VS2017) and Linux.For inefficient use of iterative operators, where not all of the indices introduced were actually referenced in the data, AIMMS used to issue a warning. For the Count, Exist, and numeric Sum, Max and Min operators, AIMMS now automatically replaces this expression by a more efficient one. In such cases, the warning will no longer be issued. Furthermore, these inefficient expressions could also be generated by the WebUI library under the hood. These expressions will now also run faster, and widgets depending on them will load faster as a result.In this release the implementation of the error handling system as described in the Language Reference, has been rebuilt. This has been done because the previous implementation had some problems that sometimes resulted in errors or warnings not being presented to the user. Although in most situations the new error handling works exactly the same, you might notice some differences in how errors or warnings are handled. If you think that this handling is incorrect, please let us know. Known changes/bug fixes:
Two new functions have been added to AIMMS: LoadDatabaseStructure and SaveDatabaseStructure. They can be used to Load/Save all currently available table structure information for the currently open database connections to a file. Using these functions, you can speed up the initialization process when accessing database tables for the first time during an AIMMS session.
Progress Window updates are now, by default, based on elapsed time instead of the number of iterations. The new option Progress Time Interval controls the progress frequency based on time. The default of the option Progress Solution has been changed to 0 (deactivated). The CPLEX and Gurobi option Progress Awareness has been removed, as well as the KNITRO option Progress Interval. The default of the SNOPT, MINOS and PATH option Solution_progress has been changed to 0 (deactivated). The default of the CPLEX and Gurobi option Barrier Progress Solution has also been changed to 0 (deactivated). Finally, the default of the Gurobi option Output File Display Interval has been changed to 1.
The latest version of AIMMS (4.3.1, Installation-free as well as PRO Package) and the latest version of PRO (2.0.2.46) support the AIMMS WebUI by default. The desktop version AIMMS will be equipped with a Tools Start WebUI menu command. In some rare cases, this menu command is not present in the latest version of AIMMS. This is most probably related to some existing previous installation of the AimmsWebUI beta. It can be resolved by uninstalling the AimmsWebUI package and rebooting your machine.Additional requirement to work with the WebUI is that you include the PRO libraries in your Project (PRO libraries can be downloaded from the PRO server, or the WebUI examples repository).We also feel it is necessary to mention that WebUI does not support clustering w.r.t. the data sessions (only w.r.t. solve sessions (as this is taken care of by AIMMS PRO)). Currently, all WebUI client sessions that are launched from PRO are running on a single machine.The postsolve step for linear models has been moved from the solver interface of CPLEX, Gurobi and CBC to AIMMS. The postsolve options of CPLEX, Gurobi and CBC have been replaced by general solvers options with similar names. Two new additional options have been added, namely Postsolve and Warning Unreliable Solution. The main advantage of this move is that the code will be easier to maintain by the AIMMS developers. The new implementation resolves several issues:
There is a new version of CPLEX, i.e., CPLEX 12.6.1.We have started working on the parallelization of the AIMMS runtime. By parallelizing calculations in AIMMS models, computation times can be significantly reduced. In this AIMMS 4.3 version there is only support for a very limited collection of parallelized expression types, and the performance improvements to be expected for most models will be very limited. With each new AIMMS release, the collection of parallelized expressions will be extended, and over time models will see increased performance until the entire engine is parallelized.The option save_new_data_pages was introduced, to control when changed data pages will be saved into your AIMMS 4 model source. The possible values are never and upon confirmation.
The persistence of both SARS and SARS-CoV-2 on cotton has been demonstrated to be significantly shorter than on non-porous surfaces [11, 25]. The data presented here also shows a significant decrease in titre of recovered virus after just 1 h drying at room temperature (20 C) the amount of virus recovered from cotton swatches was approximately 99% less than for comparable virus recovery time points for non-porous material. To verify the reduced recovery on cotton, virus was eluted 5 min after depositing on the cotton, as well as 1 h, the titre of recovered virus after 5 min was similar to that of non-porous surfaces (data not shown) suggesting the process of drying down was a significant factor for cotton material but not from the non-porous surfaces. Recovery of virus from porous substrates is also likely to be reduced compared to non-porous substrates due to adherence of the virus to the fabric fibres. When the rate of viral inactivation is considered over time rather than the gross reduction from the initial inoculum there is a more subtle difference from the non-porous surfaces. The D values for cotton at 20 C, when compared other materials, are not significantly different from other substrates (eg. 5.6 days for cotton vs. 6.3 days for vinyl), and the slopes of the line which suggests the decay rate of virus is similar across substrates. This study also demonstrates significantly longer survival times on cotton (7 days) than previous reported [11, 25]. This difference could be due to differences in the types of cotton material used, the current study used 100% cotton cloth, while previous studies used either a cotton gown or cotton t-shirt.
As NTP is entirely in UTC (Universal Time, Coordinated), Timezones and DST (Daylight Saving Time) are applied locally by the system. The file /etc/localtime is a copy of, or symlink to, a zone information file from /usr/share/zoneinfo. The RTC may be in localtime or in UTC, as specified by the 3rd line of /etc/adjtime, which will be one of LOCAL or UTC to indicate how the RTC clock has been set. Users can easily change this setting using the checkbox System Clock Uses UTC in the Date and Time graphical configuration tool. See Chapter 3, Configuring the Date and Time for information on how to use that tool. Running the RTC in UTC is recommended to avoid various problems when daylight saving time is changed.
In dimension inspection, the tolerance used as a threshold for differentiating good and defective workpieces is usually calculated in units of 5 pixels. This is based on the assumption that the number of pixels that ensures stable tolerance judgment is about 10 times the repeatability. Since the repeatability of typical machine vision is about 0.1 pixel under ideal conditions, the practical repeatability is considered to be 0.5 pixel with some margin included. Multiplying this number by 10 yields 5 pixels, and this value can be regarded as the minimum unit for tolerance setting. You can use this value to calculate the actual dimension tolerance with this formula:
When SATA disks on HPE Gen10 servers with SmartPQI controllers without expanders are hot removed and hot inserted back to a different disk bay of the same machine, or when multiple disks are hot removed and hot inserted back in a different order, sometimes a new local name is assigned to the disk. The VMFS datastore on that disk appears as a snapshot and will not be mounted back automatically because the device name has changed.
FoundationDB replicates data to two machines, so two or more machines are required to make progress. The loss of one machine can be survived without losing data, but if only two machines were present originally, the database will be unavailable until the second machine is restored, another machine is added, or the replication mode is changed.
FoundationDB stores data in triplicate, with one copy on a storage server in each of three data halls. The transaction logs are replicated four times, with two data halls containing two replicas apiece. Four available machines (two in each of two data halls) are therefore required to make progress. This configuration enables the cluster to remain available after losing a single data hall and one machine in another data hall.
FoundationDB stores data in duplicate, with one copy each on a storage server in two of three data halls. The transaction logs are replicated four times, with two data halls containing two replicas apiece. Four available machines (two in each of two data halls) are therefore required to make progress. This configuration is similar to three_data_hall, differing only in that data is stored on two instead of three replicas. This configuration is useful to unblock data distribution when a data hall becomes temporarily unavailable. Because three_data_hall_fallback reduces the redundancy level to two, it should only be used as a temporary measure to restore cluster health during a datacenter outage. 2ff7e9595c
Comments