Month: June 2024
Lookup column and List template
1.) Lookup column can return the value from another list, but can it work like excel vlookup where i can indicate col_index_num? For example, the column is looking up “staffID” column from another list, but after selection of “staffID”, it shows the “staffName” as column value.
2.) If new columns are added to a list template, how to reflect the updates in existing lists using this template? Or is it about content type? Please advice, thanks!
1.) Lookup column can return the value from another list, but can it work like excel vlookup where i can indicate col_index_num? For example, the column is looking up “staffID” column from another list, but after selection of “staffID”, it shows the “staffName” as column value.2.) If new columns are added to a list template, how to reflect the updates in existing lists using this template? Or is it about content type? Please advice, thanks! Read More
Find/Replace highlight cells with nothing in them
Hi all
Find/Replace highlight cells with nothing in them, and when I delete these cells the new ones are just the same.
Any ideas?
Hi allFind/Replace highlight cells with nothing in them, and when I delete these cells the new ones are just the same.Any ideas? Read More
Specific meeting sessions issues
Hi all,
So, we have a few members of our organisation who are keen to use Microsoft Bookings. Having the ability for them to have 1 training session but has potentially two or three dates to ensure all staff can attend would be a game changer for them.
I have gone ahead and set this up for them based on the following requirements.
Training session ‘A’ takes place on
Thursday the 4th of July (Daytime) 10:00-12:00
Saturday the 6th of July (Daytime) 10:00-12:00
Monday the 8th of July (Evening) 18:00-20:00
I have set up the service with the following settings
Availability Options
Time increments – 2 Hours
General Availability – Not bookable
Availability during these dates – (customised hours) 04/07/24 10:00 – 12:00
Availability during these dates – (customised hours) 06/07/24 10:00 – 12:00
Availability during these dates – (customised hours) 08/07/24 18:00 – 20:00
General business hours are set from 09:00 – 23:00 every day
So, in theory I want people to be given the option to book in at 10:00 or 18:00 relative to the date, however on the booking page I am being presented with an option for 11:00 or 19:00. (See example below)
Would anyone be able to help with this matter please? I’d greatly appreciate it.
Many thanks,
Matthew
Hi all, So, we have a few members of our organisation who are keen to use Microsoft Bookings. Having the ability for them to have 1 training session but has potentially two or three dates to ensure all staff can attend would be a game changer for them. I have gone ahead and set this up for them based on the following requirements. Training session ‘A’ takes place onThursday the 4th of July (Daytime) 10:00-12:00Saturday the 6th of July (Daytime) 10:00-12:00Monday the 8th of July (Evening) 18:00-20:00 I have set up the service with the following settingsAvailability OptionsTime increments – 2 HoursGeneral Availability – Not bookableAvailability during these dates – (customised hours) 04/07/24 10:00 – 12:00Availability during these dates – (customised hours) 06/07/24 10:00 – 12:00Availability during these dates – (customised hours) 08/07/24 18:00 – 20:00 General business hours are set from 09:00 – 23:00 every day So, in theory I want people to be given the option to book in at 10:00 or 18:00 relative to the date, however on the booking page I am being presented with an option for 11:00 or 19:00. (See example below) Would anyone be able to help with this matter please? I’d greatly appreciate it. Many thanks,Matthew Read More
Lock some cells for editing at the same time lock another range from pasting
Dear Community,
I have browsed several threads on the platform to find solution to this specific problem but havnt got it anywhere. I know that there is a methodology to lock the cells in a spreadsheet from editing as well as lock in formats to stop users from changing them however how do I do both in one.
For example, I have a spreadsheet in which there is a table. I would like to lock the columns A,B and C such that users are not able to edit value, at the same time I would like to lock cells in column D,E,F such that users cannot paste in values but access the drop down lists in cells to select values.
Is there anyway to achieve this?
Your inputs are highly appreciated 🙂
Dear Community, I have browsed several threads on the platform to find solution to this specific problem but havnt got it anywhere. I know that there is a methodology to lock the cells in a spreadsheet from editing as well as lock in formats to stop users from changing them however how do I do both in one. For example, I have a spreadsheet in which there is a table. I would like to lock the columns A,B and C such that users are not able to edit value, at the same time I would like to lock cells in column D,E,F such that users cannot paste in values but access the drop down lists in cells to select values. Is there anyway to achieve this? Your inputs are highly appreciated 🙂 Read More
Can you programmatically create a custom filter for Simulink model diffs?
We have some blocks in our models that we basically always want to ignore when doing a model diff, and I have made a filter for that. But as of right now, the only way to get that to other people working on the models is to export the filters, and then they manually import the filters. It would be ideal if the filters could be setup progromatically, either through the project file, or some other method to edit the definition, that way everyone would always have the same base filters.
Anyone know where the filters are defined for the user? Can I get into the xml file somewhere?We have some blocks in our models that we basically always want to ignore when doing a model diff, and I have made a filter for that. But as of right now, the only way to get that to other people working on the models is to export the filters, and then they manually import the filters. It would be ideal if the filters could be setup progromatically, either through the project file, or some other method to edit the definition, that way everyone would always have the same base filters.
Anyone know where the filters are defined for the user? Can I get into the xml file somewhere? We have some blocks in our models that we basically always want to ignore when doing a model diff, and I have made a filter for that. But as of right now, the only way to get that to other people working on the models is to export the filters, and then they manually import the filters. It would be ideal if the filters could be setup progromatically, either through the project file, or some other method to edit the definition, that way everyone would always have the same base filters.
Anyone know where the filters are defined for the user? Can I get into the xml file somewhere? simulink, model diff, visdiff MATLAB Answers — New Questions
Asynchronous readwrite via serial port (App designer)
I used serial.
and used func for serial fwrite(app.s, values, ‘uint8’, ‘async’). I could select property ‘async’ to write to serial port.
Matlab tells me: serial will be removed in a future release. Use serialport instead.
How can I use property ‘async’ for serialport? I need to write/read asynchronous via serialport.I used serial.
and used func for serial fwrite(app.s, values, ‘uint8’, ‘async’). I could select property ‘async’ to write to serial port.
Matlab tells me: serial will be removed in a future release. Use serialport instead.
How can I use property ‘async’ for serialport? I need to write/read asynchronous via serialport. I used serial.
and used func for serial fwrite(app.s, values, ‘uint8’, ‘async’). I could select property ‘async’ to write to serial port.
Matlab tells me: serial will be removed in a future release. Use serialport instead.
How can I use property ‘async’ for serialport? I need to write/read asynchronous via serialport. app designer, matlab, serial MATLAB Answers — New Questions
Error when opening a test report related to stateflow
I have several mldatx files which are related to previous test results. Until yesterday, I could open them quite good tho but I today I couldn’t open any because I get the following error on the cmd window:
failed assertion in B:matlabtoolboxstateflowsrcstateflowutilssimutils.cpp at line 261:
SLGlue::isStateflowBlock(block)
[ 0] 0x00007ffcb5d8749d C:Program FilesMATLABR2023bbinwin64stateflow.dll+13857949 SF::mx2str_write_str+00034349
[ 1] 0x00007ffcb59d9a32 C:Program FilesMATLABR2023bbinwin64stateflow.dll+10000946 SF::sf_mexFunction+00002562
[ 2] 0x00007ffcb59d903c C:Program FilesMATLABR2023bbinwin64stateflow.dll+09998396 SF::sf_mexFunction+00000012
[ 3] 0x00007ffd72156f89 C:Program FilesMATLABR2023bbinwin64libmex.dll+00683913 mexfile::Inspector::needs_upgrade+00023257
[ 4] 0x00007ffd7215a002 C:Program FilesMATLABR2023bbinwin64libmex.dll+00696322 MexRetrieveVersion+00009682
[ 5] 0x00007ffd7215a327 C:Program FilesMATLABR2023bbinwin64libmex.dll+00697127 MexRetrieveVersion+00010487
[ 6] 0x00007ffd7213b2ce C:Program FilesMATLABR2023bbinwin64libmex.dll+00570062 mexUnlock+00016942
[ 7] 0x00007ffd757245a2 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01263010 Mfh_file::dispatch_file_common+00000178
[ 8] 0x00007ffd75723802 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01259522 Mfh_error::lookup+00012722
[ 9] 0x00007ffd757244dd C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01262813 Mfh_file::dispatch+00000045
[ 10] 0x00007ffd718f705d C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00421981 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00313389
[ 11] 0x00007ffd71906c3e C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00486462 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00377870
[ 12] 0x00007ffd47f0a93e C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06072638 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00006318
[ 13] 0x00007ffd47f0ca18 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06081048 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00014728
[ 14] 0x00007ffd47e41438 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+05248056 MathWorks::lxe::XvalueFactory::XvalueDeleter::XvalueDeleter+00212072
[ 15] 0x00007ffd47e5e379 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+05366649 MathWorks::lxe::XvalueFactory::XvalueDeleter::XvalueDeleter+00330665
[ 16] 0x00007ffd47d191c7 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+04035015 MathWorks::lxe::GetTag+00006663
[ 17] 0x00007ffd47d034f8 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+03945720 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00041688
[ 18] 0x00007ffd47d078c0 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+03963072 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00059040
[ 19] 0x00007ffd719f5790 C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+01464208 FeatureTestObservableWorkspace+00211120
[ 20] 0x00007ffd718eee3b C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00388667 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00280075
[ 21] 0x00007ffd718eeabc C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00387772 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00279180
[ 22] 0x00007ffd718f14f2 C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00398578 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00289986
[ 23] 0x00007ffd757245a2 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01263010 Mfh_file::dispatch_file_common+00000178
[ 24] 0x00007ffd75723228 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01258024 Mfh_error::lookup+00011224
[ 25] 0x00007ffd7572449d C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01262749 Mfh_file::dispatch+00000045
[ 26] 0x00007ffd31a65ff6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+03825654 mwboost::archive::detail::oserializer<mwboost::archive::text_oarchive,MathWorks::MatlabComponents::ComponentIdentifier>::save_object_data+00306918
[ 27] 0x00007ffd31993947 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02963783 mcos::heterogeneous::mcosIsHeterogeneousArray+00051367
[ 28] 0x00007ffd31993af1 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02964209 mcos::heterogeneous::mcosIsHeterogeneousArray+00051793
[ 29] 0x00007ffd31993f8f C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02965391 mcos::heterogeneous::mcosIsHeterogeneousArray+00052975
[ 30] 0x00007ffd31997c7c C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02980988 mcos::heterogeneous::mcosIsHeterogeneousArray+00068572
[ 31] 0x00007ffd31aa35e6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+04077030 namedArgsToCell+00000870
[ 32] 0x00007ffd31ba614f C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+05136719 musBeA+00328719
[ 33] 0x00007ffd31ba4aa6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+05130918 musBeA+00322918
[ 34] 0x00007ffd755fc07f C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00049279
[ 35] 0x00007ffd7561d76d C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00186221 Mfh_MATLAB_fn_impl::dispatch_with_reuse+00000045
[ 36] 0x00007ffd47f3ac70 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06270064 MathWorks::lxe::CreateUnboundFunctionHandle+00011168
[ 37] 0x00007ffd7193ef8d C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00716685 mwboost::archive::detail::pointer_oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::PreLineExecutionEvent>::save_object_ptr+00086333
[ 38] 0x00007ffd719b952f C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+01217839 mwboost::archive::detail::oserializer<mwboost::archive::text_oarchive,MathWorks::MatlabComponents::ComponentIdentifier>::save_object_data+00323199
[ 39] 0x00007ffd75357ed5 C:Program FilesMATLABR2023bbinwin64m_interpreter.dll+00753365 inCallFcn+00000069
[ 40] 0x00007ffd45437216 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02585110 slsv::mxw::WarningHandler::operator=+00004918
[ 41] 0x00007ffd4544bcde C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02669790 CMatlabCommand::execute+00000190
[ 42] 0x00007ffd4545c8e4 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02738404 slsvFEVAL_NoThrow+00000276
[ 43] 0x00007ffd4545c7c4 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02738116 slsvFEVAL_NoThrow+00000068
[ 44] 0x00007ffca39e5898 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07755928 stm_util::lookup<stm::CoverageMetrics>+00010120
[ 45] 0x00007ffca39ea4ad C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07775405 stm_util::lookup<stm::CoverageMetrics>+00029597
[ 46] 0x00007ffca39ed7a3 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07788451 stm_util::lookup<stm::CoverageMetrics>+00042643
[ 47] 0x00007ffd09c93044 C:Program FilesMATLABR2023bbinwin64dmr.dll+00274500 dmr::ObjectRef::objectID+00003668
[ 48] 0x00007ffd09c92f30 C:Program FilesMATLABR2023bbinwin64dmr.dll+00274224 dmr::ObjectRef::objectID+00003392
[ 49] 0x00007ffcf44891bf C:Program FilesMATLABR2023bbinwin64simulation_data_repository.dll+00823743 sdi::ObjectManager::safeTransaction+00000095
[ 50] 0x00007ffca39eaae9 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07777001 stm_util::lookup<stm::CoverageMetrics>+00031193
[ 51] 0x00007ffca3b6fc4e C:Program FilesMATLABR2023bbinwin64libmwstm.dll+09370702 stm::msgservice::unsubscribeAll+00110030
[ 52] 0x00007ffca3557fe4 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+02981860
[ 53] 0x00007ffca358df00 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+03202816 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00032240
[ 54] 0x00007ffd75908c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 55] 0x00007ffd731a58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 56] 0x00007ffd758dcbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 57] 0x00007ffd758acc61 C:Program FilesMATLABR2023bbinwin64iqm.dll+00445537 iqm::Iqm::create+00007745
[ 58] 0x00007ffd71fa3f5e C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081758 ioReadLine+00000430
[ 59] 0x00007ffd71fa3d75 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081269 ioReadLine+00000165
[ 60] 0x00007ffd71fd5fb0 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00286640 mnGetCommandLineBuffer+00000288
[ 61] 0x00007ffd71fd64b2 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00287922 mnParser+00000578
[ 62] 0x00007ffd731ab398 C:Program FilesMATLABR2023bbinwin64mcr.dll+00439192 mcr_initialize_main+00013816
[ 63] 0x00007ffd73158604 C:Program FilesMATLABR2023bbinwin64mcr.dll+00099844 mcrFunctionSignature::set_signature+00078996
[ 64] 0x00007ffd731761a0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00221600 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00017728
[ 65] 0x00007ffd75908c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 66] 0x00007ffd731a58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 67] 0x00007ffd758dcbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 68] 0x00007ffd758ade81 C:Program FilesMATLABR2023bbinwin64iqm.dll+00450177 iqm::Iqm::create+00012385
[ 69] 0x00007ffd758ad5c9 C:Program FilesMATLABR2023bbinwin64iqm.dll+00447945 iqm::Iqm::create+00010153
[ 70] 0x00007ffd73191c1c C:Program FilesMATLABR2023bbinwin64mcr.dll+00334876 mcrInstantiationError::operator=+00009948
[ 71] 0x00007ffd73192645 C:Program FilesMATLABR2023bbinwin64mcr.dll+00337477 mcrInstantiationError::operator=+00012549
[ 72] 0x00007ffd7318ffd0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00327632 mcrInstantiationError::operator=+00002704
[ 73] 0x00007ffe069892ea C:Program FilesMATLABR2023bbinwin64mwboost_thread-vc142-mt-x64-1_78.dll+00037610 mwboost::detail::win32::handle_manager::swap+00001642
[ 74] 0x00007ffe22dd9333 C:WINDOWSSystem32ucrtbase.dll+00168755 recalloc+00000163
[ 75] 0x00007ffe240d257d C:WINDOWSSystem32KERNEL32.DLL+00075133 BaseThreadInitThunk+00000029
[ 76] 0x00007ffe251eaf28 C:WINDOWSSYSTEM32ntdll.dll+00372520 RtlUserThreadStart+00000040
MATLAB stack trace:
> In cvi.TopModelCov.updateModelHandles>get_sf_block_instance_handle
In cvi.TopModelCov.updateModelHandles>update_sf_chart_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles
In cvi.ReportUtils.checkModelLoaded
In cvi.ReportUtils.loadTopModelAndRefModels>checkModelLoaded
In cvi.ReportUtils.loadTopModelAndRefModels>checkModelLoadedForCovdata
In cvi.ReportUtils.loadTopModelAndRefModels
In cvmodelview
In stm.internal.Coverage.safeSlvnv
In stm.internal.Coverage.modelViewI have several mldatx files which are related to previous test results. Until yesterday, I could open them quite good tho but I today I couldn’t open any because I get the following error on the cmd window:
failed assertion in B:matlabtoolboxstateflowsrcstateflowutilssimutils.cpp at line 261:
SLGlue::isStateflowBlock(block)
[ 0] 0x00007ffcb5d8749d C:Program FilesMATLABR2023bbinwin64stateflow.dll+13857949 SF::mx2str_write_str+00034349
[ 1] 0x00007ffcb59d9a32 C:Program FilesMATLABR2023bbinwin64stateflow.dll+10000946 SF::sf_mexFunction+00002562
[ 2] 0x00007ffcb59d903c C:Program FilesMATLABR2023bbinwin64stateflow.dll+09998396 SF::sf_mexFunction+00000012
[ 3] 0x00007ffd72156f89 C:Program FilesMATLABR2023bbinwin64libmex.dll+00683913 mexfile::Inspector::needs_upgrade+00023257
[ 4] 0x00007ffd7215a002 C:Program FilesMATLABR2023bbinwin64libmex.dll+00696322 MexRetrieveVersion+00009682
[ 5] 0x00007ffd7215a327 C:Program FilesMATLABR2023bbinwin64libmex.dll+00697127 MexRetrieveVersion+00010487
[ 6] 0x00007ffd7213b2ce C:Program FilesMATLABR2023bbinwin64libmex.dll+00570062 mexUnlock+00016942
[ 7] 0x00007ffd757245a2 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01263010 Mfh_file::dispatch_file_common+00000178
[ 8] 0x00007ffd75723802 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01259522 Mfh_error::lookup+00012722
[ 9] 0x00007ffd757244dd C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01262813 Mfh_file::dispatch+00000045
[ 10] 0x00007ffd718f705d C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00421981 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00313389
[ 11] 0x00007ffd71906c3e C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00486462 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00377870
[ 12] 0x00007ffd47f0a93e C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06072638 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00006318
[ 13] 0x00007ffd47f0ca18 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06081048 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00014728
[ 14] 0x00007ffd47e41438 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+05248056 MathWorks::lxe::XvalueFactory::XvalueDeleter::XvalueDeleter+00212072
[ 15] 0x00007ffd47e5e379 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+05366649 MathWorks::lxe::XvalueFactory::XvalueDeleter::XvalueDeleter+00330665
[ 16] 0x00007ffd47d191c7 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+04035015 MathWorks::lxe::GetTag+00006663
[ 17] 0x00007ffd47d034f8 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+03945720 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00041688
[ 18] 0x00007ffd47d078c0 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+03963072 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00059040
[ 19] 0x00007ffd719f5790 C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+01464208 FeatureTestObservableWorkspace+00211120
[ 20] 0x00007ffd718eee3b C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00388667 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00280075
[ 21] 0x00007ffd718eeabc C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00387772 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00279180
[ 22] 0x00007ffd718f14f2 C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00398578 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00289986
[ 23] 0x00007ffd757245a2 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01263010 Mfh_file::dispatch_file_common+00000178
[ 24] 0x00007ffd75723228 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01258024 Mfh_error::lookup+00011224
[ 25] 0x00007ffd7572449d C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01262749 Mfh_file::dispatch+00000045
[ 26] 0x00007ffd31a65ff6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+03825654 mwboost::archive::detail::oserializer<mwboost::archive::text_oarchive,MathWorks::MatlabComponents::ComponentIdentifier>::save_object_data+00306918
[ 27] 0x00007ffd31993947 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02963783 mcos::heterogeneous::mcosIsHeterogeneousArray+00051367
[ 28] 0x00007ffd31993af1 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02964209 mcos::heterogeneous::mcosIsHeterogeneousArray+00051793
[ 29] 0x00007ffd31993f8f C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02965391 mcos::heterogeneous::mcosIsHeterogeneousArray+00052975
[ 30] 0x00007ffd31997c7c C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02980988 mcos::heterogeneous::mcosIsHeterogeneousArray+00068572
[ 31] 0x00007ffd31aa35e6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+04077030 namedArgsToCell+00000870
[ 32] 0x00007ffd31ba614f C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+05136719 musBeA+00328719
[ 33] 0x00007ffd31ba4aa6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+05130918 musBeA+00322918
[ 34] 0x00007ffd755fc07f C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00049279
[ 35] 0x00007ffd7561d76d C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00186221 Mfh_MATLAB_fn_impl::dispatch_with_reuse+00000045
[ 36] 0x00007ffd47f3ac70 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06270064 MathWorks::lxe::CreateUnboundFunctionHandle+00011168
[ 37] 0x00007ffd7193ef8d C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00716685 mwboost::archive::detail::pointer_oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::PreLineExecutionEvent>::save_object_ptr+00086333
[ 38] 0x00007ffd719b952f C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+01217839 mwboost::archive::detail::oserializer<mwboost::archive::text_oarchive,MathWorks::MatlabComponents::ComponentIdentifier>::save_object_data+00323199
[ 39] 0x00007ffd75357ed5 C:Program FilesMATLABR2023bbinwin64m_interpreter.dll+00753365 inCallFcn+00000069
[ 40] 0x00007ffd45437216 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02585110 slsv::mxw::WarningHandler::operator=+00004918
[ 41] 0x00007ffd4544bcde C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02669790 CMatlabCommand::execute+00000190
[ 42] 0x00007ffd4545c8e4 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02738404 slsvFEVAL_NoThrow+00000276
[ 43] 0x00007ffd4545c7c4 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02738116 slsvFEVAL_NoThrow+00000068
[ 44] 0x00007ffca39e5898 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07755928 stm_util::lookup<stm::CoverageMetrics>+00010120
[ 45] 0x00007ffca39ea4ad C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07775405 stm_util::lookup<stm::CoverageMetrics>+00029597
[ 46] 0x00007ffca39ed7a3 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07788451 stm_util::lookup<stm::CoverageMetrics>+00042643
[ 47] 0x00007ffd09c93044 C:Program FilesMATLABR2023bbinwin64dmr.dll+00274500 dmr::ObjectRef::objectID+00003668
[ 48] 0x00007ffd09c92f30 C:Program FilesMATLABR2023bbinwin64dmr.dll+00274224 dmr::ObjectRef::objectID+00003392
[ 49] 0x00007ffcf44891bf C:Program FilesMATLABR2023bbinwin64simulation_data_repository.dll+00823743 sdi::ObjectManager::safeTransaction+00000095
[ 50] 0x00007ffca39eaae9 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07777001 stm_util::lookup<stm::CoverageMetrics>+00031193
[ 51] 0x00007ffca3b6fc4e C:Program FilesMATLABR2023bbinwin64libmwstm.dll+09370702 stm::msgservice::unsubscribeAll+00110030
[ 52] 0x00007ffca3557fe4 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+02981860
[ 53] 0x00007ffca358df00 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+03202816 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00032240
[ 54] 0x00007ffd75908c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 55] 0x00007ffd731a58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 56] 0x00007ffd758dcbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 57] 0x00007ffd758acc61 C:Program FilesMATLABR2023bbinwin64iqm.dll+00445537 iqm::Iqm::create+00007745
[ 58] 0x00007ffd71fa3f5e C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081758 ioReadLine+00000430
[ 59] 0x00007ffd71fa3d75 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081269 ioReadLine+00000165
[ 60] 0x00007ffd71fd5fb0 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00286640 mnGetCommandLineBuffer+00000288
[ 61] 0x00007ffd71fd64b2 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00287922 mnParser+00000578
[ 62] 0x00007ffd731ab398 C:Program FilesMATLABR2023bbinwin64mcr.dll+00439192 mcr_initialize_main+00013816
[ 63] 0x00007ffd73158604 C:Program FilesMATLABR2023bbinwin64mcr.dll+00099844 mcrFunctionSignature::set_signature+00078996
[ 64] 0x00007ffd731761a0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00221600 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00017728
[ 65] 0x00007ffd75908c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 66] 0x00007ffd731a58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 67] 0x00007ffd758dcbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 68] 0x00007ffd758ade81 C:Program FilesMATLABR2023bbinwin64iqm.dll+00450177 iqm::Iqm::create+00012385
[ 69] 0x00007ffd758ad5c9 C:Program FilesMATLABR2023bbinwin64iqm.dll+00447945 iqm::Iqm::create+00010153
[ 70] 0x00007ffd73191c1c C:Program FilesMATLABR2023bbinwin64mcr.dll+00334876 mcrInstantiationError::operator=+00009948
[ 71] 0x00007ffd73192645 C:Program FilesMATLABR2023bbinwin64mcr.dll+00337477 mcrInstantiationError::operator=+00012549
[ 72] 0x00007ffd7318ffd0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00327632 mcrInstantiationError::operator=+00002704
[ 73] 0x00007ffe069892ea C:Program FilesMATLABR2023bbinwin64mwboost_thread-vc142-mt-x64-1_78.dll+00037610 mwboost::detail::win32::handle_manager::swap+00001642
[ 74] 0x00007ffe22dd9333 C:WINDOWSSystem32ucrtbase.dll+00168755 recalloc+00000163
[ 75] 0x00007ffe240d257d C:WINDOWSSystem32KERNEL32.DLL+00075133 BaseThreadInitThunk+00000029
[ 76] 0x00007ffe251eaf28 C:WINDOWSSYSTEM32ntdll.dll+00372520 RtlUserThreadStart+00000040
MATLAB stack trace:
> In cvi.TopModelCov.updateModelHandles>get_sf_block_instance_handle
In cvi.TopModelCov.updateModelHandles>update_sf_chart_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles
In cvi.ReportUtils.checkModelLoaded
In cvi.ReportUtils.loadTopModelAndRefModels>checkModelLoaded
In cvi.ReportUtils.loadTopModelAndRefModels>checkModelLoadedForCovdata
In cvi.ReportUtils.loadTopModelAndRefModels
In cvmodelview
In stm.internal.Coverage.safeSlvnv
In stm.internal.Coverage.modelView I have several mldatx files which are related to previous test results. Until yesterday, I could open them quite good tho but I today I couldn’t open any because I get the following error on the cmd window:
failed assertion in B:matlabtoolboxstateflowsrcstateflowutilssimutils.cpp at line 261:
SLGlue::isStateflowBlock(block)
[ 0] 0x00007ffcb5d8749d C:Program FilesMATLABR2023bbinwin64stateflow.dll+13857949 SF::mx2str_write_str+00034349
[ 1] 0x00007ffcb59d9a32 C:Program FilesMATLABR2023bbinwin64stateflow.dll+10000946 SF::sf_mexFunction+00002562
[ 2] 0x00007ffcb59d903c C:Program FilesMATLABR2023bbinwin64stateflow.dll+09998396 SF::sf_mexFunction+00000012
[ 3] 0x00007ffd72156f89 C:Program FilesMATLABR2023bbinwin64libmex.dll+00683913 mexfile::Inspector::needs_upgrade+00023257
[ 4] 0x00007ffd7215a002 C:Program FilesMATLABR2023bbinwin64libmex.dll+00696322 MexRetrieveVersion+00009682
[ 5] 0x00007ffd7215a327 C:Program FilesMATLABR2023bbinwin64libmex.dll+00697127 MexRetrieveVersion+00010487
[ 6] 0x00007ffd7213b2ce C:Program FilesMATLABR2023bbinwin64libmex.dll+00570062 mexUnlock+00016942
[ 7] 0x00007ffd757245a2 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01263010 Mfh_file::dispatch_file_common+00000178
[ 8] 0x00007ffd75723802 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01259522 Mfh_error::lookup+00012722
[ 9] 0x00007ffd757244dd C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01262813 Mfh_file::dispatch+00000045
[ 10] 0x00007ffd718f705d C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00421981 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00313389
[ 11] 0x00007ffd71906c3e C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00486462 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00377870
[ 12] 0x00007ffd47f0a93e C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06072638 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00006318
[ 13] 0x00007ffd47f0ca18 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06081048 MathWorks::lxe::ReadOnlyXvaluePtr::operator=+00014728
[ 14] 0x00007ffd47e41438 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+05248056 MathWorks::lxe::XvalueFactory::XvalueDeleter::XvalueDeleter+00212072
[ 15] 0x00007ffd47e5e379 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+05366649 MathWorks::lxe::XvalueFactory::XvalueDeleter::XvalueDeleter+00330665
[ 16] 0x00007ffd47d191c7 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+04035015 MathWorks::lxe::GetTag+00006663
[ 17] 0x00007ffd47d034f8 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+03945720 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00041688
[ 18] 0x00007ffd47d078c0 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+03963072 MathWorks::lxe::SetEngineImplUnlinkFlagForAllCallsOnStack+00059040
[ 19] 0x00007ffd719f5790 C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+01464208 FeatureTestObservableWorkspace+00211120
[ 20] 0x00007ffd718eee3b C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00388667 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00280075
[ 21] 0x00007ffd718eeabc C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00387772 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00279180
[ 22] 0x00007ffd718f14f2 C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00398578 mwboost::archive::codecvt_null<wchar_t>::do_max_length+00289986
[ 23] 0x00007ffd757245a2 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01263010 Mfh_file::dispatch_file_common+00000178
[ 24] 0x00007ffd75723228 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01258024 Mfh_error::lookup+00011224
[ 25] 0x00007ffd7572449d C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+01262749 Mfh_file::dispatch+00000045
[ 26] 0x00007ffd31a65ff6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+03825654 mwboost::archive::detail::oserializer<mwboost::archive::text_oarchive,MathWorks::MatlabComponents::ComponentIdentifier>::save_object_data+00306918
[ 27] 0x00007ffd31993947 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02963783 mcos::heterogeneous::mcosIsHeterogeneousArray+00051367
[ 28] 0x00007ffd31993af1 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02964209 mcos::heterogeneous::mcosIsHeterogeneousArray+00051793
[ 29] 0x00007ffd31993f8f C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02965391 mcos::heterogeneous::mcosIsHeterogeneousArray+00052975
[ 30] 0x00007ffd31997c7c C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+02980988 mcos::heterogeneous::mcosIsHeterogeneousArray+00068572
[ 31] 0x00007ffd31aa35e6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+04077030 namedArgsToCell+00000870
[ 32] 0x00007ffd31ba614f C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+05136719 musBeA+00328719
[ 33] 0x00007ffd31ba4aa6 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+05130918 musBeA+00322918
[ 34] 0x00007ffd755fc07f C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00049279
[ 35] 0x00007ffd7561d76d C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00186221 Mfh_MATLAB_fn_impl::dispatch_with_reuse+00000045
[ 36] 0x00007ffd47f3ac70 C:Program FilesMATLABR2023bbinwin64m_lxe.dll+06270064 MathWorks::lxe::CreateUnboundFunctionHandle+00011168
[ 37] 0x00007ffd7193ef8d C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+00716685 mwboost::archive::detail::pointer_oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::PreLineExecutionEvent>::save_object_ptr+00086333
[ 38] 0x00007ffd719b952f C:Program FilesMATLABR2023bbinwin64libmwlxemainservices.dll+01217839 mwboost::archive::detail::oserializer<mwboost::archive::text_oarchive,MathWorks::MatlabComponents::ComponentIdentifier>::save_object_data+00323199
[ 39] 0x00007ffd75357ed5 C:Program FilesMATLABR2023bbinwin64m_interpreter.dll+00753365 inCallFcn+00000069
[ 40] 0x00007ffd45437216 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02585110 slsv::mxw::WarningHandler::operator=+00004918
[ 41] 0x00007ffd4544bcde C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02669790 CMatlabCommand::execute+00000190
[ 42] 0x00007ffd4545c8e4 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02738404 slsvFEVAL_NoThrow+00000276
[ 43] 0x00007ffd4545c7c4 C:Program FilesMATLABR2023bbinwin64libmwsl_services.dll+02738116 slsvFEVAL_NoThrow+00000068
[ 44] 0x00007ffca39e5898 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07755928 stm_util::lookup<stm::CoverageMetrics>+00010120
[ 45] 0x00007ffca39ea4ad C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07775405 stm_util::lookup<stm::CoverageMetrics>+00029597
[ 46] 0x00007ffca39ed7a3 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07788451 stm_util::lookup<stm::CoverageMetrics>+00042643
[ 47] 0x00007ffd09c93044 C:Program FilesMATLABR2023bbinwin64dmr.dll+00274500 dmr::ObjectRef::objectID+00003668
[ 48] 0x00007ffd09c92f30 C:Program FilesMATLABR2023bbinwin64dmr.dll+00274224 dmr::ObjectRef::objectID+00003392
[ 49] 0x00007ffcf44891bf C:Program FilesMATLABR2023bbinwin64simulation_data_repository.dll+00823743 sdi::ObjectManager::safeTransaction+00000095
[ 50] 0x00007ffca39eaae9 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+07777001 stm_util::lookup<stm::CoverageMetrics>+00031193
[ 51] 0x00007ffca3b6fc4e C:Program FilesMATLABR2023bbinwin64libmwstm.dll+09370702 stm::msgservice::unsubscribeAll+00110030
[ 52] 0x00007ffca3557fe4 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+02981860
[ 53] 0x00007ffca358df00 C:Program FilesMATLABR2023bbinwin64libmwstm.dll+03202816 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00032240
[ 54] 0x00007ffd75908c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 55] 0x00007ffd731a58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 56] 0x00007ffd758dcbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 57] 0x00007ffd758acc61 C:Program FilesMATLABR2023bbinwin64iqm.dll+00445537 iqm::Iqm::create+00007745
[ 58] 0x00007ffd71fa3f5e C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081758 ioReadLine+00000430
[ 59] 0x00007ffd71fa3d75 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081269 ioReadLine+00000165
[ 60] 0x00007ffd71fd5fb0 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00286640 mnGetCommandLineBuffer+00000288
[ 61] 0x00007ffd71fd64b2 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00287922 mnParser+00000578
[ 62] 0x00007ffd731ab398 C:Program FilesMATLABR2023bbinwin64mcr.dll+00439192 mcr_initialize_main+00013816
[ 63] 0x00007ffd73158604 C:Program FilesMATLABR2023bbinwin64mcr.dll+00099844 mcrFunctionSignature::set_signature+00078996
[ 64] 0x00007ffd731761a0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00221600 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00017728
[ 65] 0x00007ffd75908c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 66] 0x00007ffd731a58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 67] 0x00007ffd758dcbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 68] 0x00007ffd758ade81 C:Program FilesMATLABR2023bbinwin64iqm.dll+00450177 iqm::Iqm::create+00012385
[ 69] 0x00007ffd758ad5c9 C:Program FilesMATLABR2023bbinwin64iqm.dll+00447945 iqm::Iqm::create+00010153
[ 70] 0x00007ffd73191c1c C:Program FilesMATLABR2023bbinwin64mcr.dll+00334876 mcrInstantiationError::operator=+00009948
[ 71] 0x00007ffd73192645 C:Program FilesMATLABR2023bbinwin64mcr.dll+00337477 mcrInstantiationError::operator=+00012549
[ 72] 0x00007ffd7318ffd0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00327632 mcrInstantiationError::operator=+00002704
[ 73] 0x00007ffe069892ea C:Program FilesMATLABR2023bbinwin64mwboost_thread-vc142-mt-x64-1_78.dll+00037610 mwboost::detail::win32::handle_manager::swap+00001642
[ 74] 0x00007ffe22dd9333 C:WINDOWSSystem32ucrtbase.dll+00168755 recalloc+00000163
[ 75] 0x00007ffe240d257d C:WINDOWSSystem32KERNEL32.DLL+00075133 BaseThreadInitThunk+00000029
[ 76] 0x00007ffe251eaf28 C:WINDOWSSYSTEM32ntdll.dll+00372520 RtlUserThreadStart+00000040
MATLAB stack trace:
> In cvi.TopModelCov.updateModelHandles>get_sf_block_instance_handle
In cvi.TopModelCov.updateModelHandles>update_sf_chart_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles>update_susbsys_handles
In cvi.TopModelCov.updateModelHandles
In cvi.ReportUtils.checkModelLoaded
In cvi.ReportUtils.loadTopModelAndRefModels>checkModelLoaded
In cvi.ReportUtils.loadTopModelAndRefModels>checkModelLoadedForCovdata
In cvi.ReportUtils.loadTopModelAndRefModels
In cvmodelview
In stm.internal.Coverage.safeSlvnv
In stm.internal.Coverage.modelView stateflow, testing, simulink, test MATLAB Answers — New Questions
statement in test assessment block
how can i verify output (multiple statements)w.r.t time in test assessment block , for example-(if t==1 ,verify (out== 1 ) ) (if t==2,verify (out== 2) )……..(if t==8 ,verify (out== 8 ) ) can we use any loops in test assement block in simulink test ?
for t=1:8
if t==i
verify(out==i)
end
this for loop showing error.how can i verify output (multiple statements)w.r.t time in test assessment block , for example-(if t==1 ,verify (out== 1 ) ) (if t==2,verify (out== 2) )……..(if t==8 ,verify (out== 8 ) ) can we use any loops in test assement block in simulink test ?
for t=1:8
if t==i
verify(out==i)
end
this for loop showing error. how can i verify output (multiple statements)w.r.t time in test assessment block , for example-(if t==1 ,verify (out== 1 ) ) (if t==2,verify (out== 2) )……..(if t==8 ,verify (out== 8 ) ) can we use any loops in test assement block in simulink test ?
for t=1:8
if t==i
verify(out==i)
end
this for loop showing error. test manager, test assement block MATLAB Answers — New Questions
Create Plans from Planner Plans
There are very many Planner plans (Included tier) around the organization. I want to import these into Planner Plans (Planner Plan 1 & Project Plan 3 i.e. ‘Project for web’) so that they can be included in a Roadmap (Project Plan 3 tier).
How do I do that, please?
Thank you
There are very many Planner plans (Included tier) around the organization. I want to import these into Planner Plans (Planner Plan 1 & Project Plan 3 i.e. ‘Project for web’) so that they can be included in a Roadmap (Project Plan 3 tier). How do I do that, please? Thank you Read More
Upgrade SP2016 to hybrid with one drive
Hi,
My organization is currently running on SP2016 on-premises without one drive access. Recently, we have kicked off discussions to upgrade SP2016 to Hybrid with one drive for file storage.
We use MS365 for teams and other desktop apps such as excel, word, PowerPoint etc. I was wondering if we go down the path of upgrading to hybrid solution, then:
Do we need to setup one drive in hybrid environment?
Can we use one drive to replace network shares for file storage?
what sort of configuration do we need to put in place to store sensitive documents with security labels?
Any input will be highly appreciated.
Thanks
Hi, My organization is currently running on SP2016 on-premises without one drive access. Recently, we have kicked off discussions to upgrade SP2016 to Hybrid with one drive for file storage. We use MS365 for teams and other desktop apps such as excel, word, PowerPoint etc. I was wondering if we go down the path of upgrading to hybrid solution, then: Do we need to setup one drive in hybrid environment?Can we use one drive to replace network shares for file storage?what sort of configuration do we need to put in place to store sensitive documents with security labels? Any input will be highly appreciated. Thanks Read More
Recommend me a safe & best YouTube to mp3 converter for my Windows 11
I’m currently on the lookout for a reliable and safe YouTube to MP3 converter that works seamlessly on Windows 11. I need a tool that can efficiently convert videos to high-quality audio files, ideally without compromising on sound quality. Additionally, it’s important that the software is user-friendly and free from excessive ads or security risks. If anyone has recommendations for such a tool, especially one that has proven to be dependable over time, please share your experiences. Your input will be greatly appreciated as it will help streamline my workflow and enhance my multimedia projects.
I’m currently on the lookout for a reliable and safe YouTube to MP3 converter that works seamlessly on Windows 11. I need a tool that can efficiently convert videos to high-quality audio files, ideally without compromising on sound quality. Additionally, it’s important that the software is user-friendly and free from excessive ads or security risks. If anyone has recommendations for such a tool, especially one that has proven to be dependable over time, please share your experiences. Your input will be greatly appreciated as it will help streamline my workflow and enhance my multimedia projects. Read More
Why is My Quick-Books pay-roll update not working after update?
Quick-Books pay-roll update not working. Getting errors during the update process. How can I resolve this issue and ensure my pay-roll updates successfully?
Quick-Books pay-roll update not working. Getting errors during the update process. How can I resolve this issue and ensure my pay-roll updates successfully? Read More
How to Fix Quick-Books Error 1920 after windows update?
What is Quick-Books Error 1920, and how can I fix it? I’m having trouble installing Quick-Books Desktop due to this error.
What is Quick-Books Error 1920, and how can I fix it? I’m having trouble installing Quick-Books Desktop due to this error. Read More
Exchange admin center Delegation permissions error
I am having a strange issue with Exchange Admin Centre
I am signed in as a Global Administrator but when I go to a user’s mailbox and then to the delegation tab I get the following error.
Error:
I am having a strange issue with Exchange Admin Centre I am signed in as a Global Administrator but when I go to a user’s mailbox and then to the delegation tab I get the following error. Failed to get mailbox permissionsError:User is not allowed to call Get-MailboxPermission Is this a bug? I wouldn’t think it was a permissions issue as I have been fine for years with my current ones. Read More
How to Resolve Quick-Books Database Manager failed to start issue after update?
I am facing an issue where the Quick-Books Database Manager failed to start. What could be causing this, and what are the possible troubleshooting steps to resolve it?
I am facing an issue where the Quick-Books Database Manager failed to start. What could be causing this, and what are the possible troubleshooting steps to resolve it? Read More
Platform engineering: Monitor Backstage with Application Insights
The platform engineering journey requires abundant information to make informed decisions. Understanding how developers use the platform—how frequently and for how long—is invaluable. Since the internal developer portal (IDP) serves as the central hub for developers’ regular tasks, it becomes the ideal location for monitoring these activities and collecting essential data.
Backstage, a common IDP implementation, provides an excellent opportunity to demonstrate how to integrate monitoring. In this article, we’ll explore how to add monitoring to the Backstage portal using Azure Monitor, specifically Application Insights.
Upon reviewing the Backstage documentation, we find that the portal is already instrumented using OpenTelemetry. Furthermore, Application Insights is a supported provider for OpenTelemetry.
This is excellent news, as it streamlines the process and saves time that would otherwise be spent manually adding tracing calls to the Backstage code.
To enable OpenTelemetry instrumentation, follow the steps in the official documentation(https://backstage.io/docs/tutorials/setup-opentelemetry/). Start by adding the required packages using the following command:
yarn –cwd packages/backend add
@opentelemetry/sdk-node
@opentelemetry/auto-instrumentations-node
/monitor-opentelemetry-exporter
Next, create a new file named instrumentation.js inside the backend/src folder.
The content of the file should be:
const { NodeSDK } = require(‘@opentelemetry/sdk-node’);
const {
getNodeAutoInstrumentations,
} = require(‘@opentelemetry/auto-instrumentations-node’);
const { AzureMonitorTraceExporter } = require(“@azure/monitor-opentelemetry-exporter”);
const { AzureMonitorMetricExporter } = require(“@azure/monitor-opentelemetry-exporter”);
// Create an exporter instance
const azTraceExporter = new AzureMonitorTraceExporter({
connectionString:
process.env[“APPLICATIONINSIGHTS_CONNECTION_STRING”] || “<YourAppInsightsConnectionString>”
});
const sdk = new NodeSDK({
traceExporter: azTraceExporter,
instrumentations: [getNodeAutoInstrumentations()],
});
sdk.start();
And with that…we are done!
Browse some pages within the Backstage portal and in a few minutes, telemetry will be available in Application Insights.
Here are some samples of information that has been gathered. All this information is out-of-the-box reports, so without any other customization, we can obtain a wealth of information.
We can check if the portal is returning errors, if the response time is within acceptable parameters, how many requests are made and the usage pattern…
Examine the details of a request to Backstage, the time taken to serve the request and the time spent on all dependencies…
Retrieve information from the accessed URLs, for example, to identify the most common searches and ascertain developers’ interests.
Microsoft Tech Community – Latest Blogs –Read More
Matter WakeUp System AI
Project Overview
Developed in partnership with UCL, Great Ormond Street Hospital (GOSH) and Intel, the WakeUp System provides reassurance and support to patients with disabilities in long-term care and the elderly. As mentioned previously, one of the system’s main objectives is to enable them to autonomously control their environment, and it is designed for use in both hospital and home settings. Moreover, the project encompasses a research study in Intel’s new OpenVINO project.
The system architecture is divided into three parts: triggers, targets and the WakeUp system. The WakeUp system acts as a message broker, connecting a patient’s commands to an appropriate target device and enabling actions to be performed. The system can be configured by a healthcare professional or by the patient using a graphical user interface (GUI).
The WakeUp System represents a promising idea in healthcare technology innovation. It has the potential to improve the quality of life and efficiency of healthcare services for disabled patients. This report provides a comprehensive overview of the design concept, the technical implementation of the project and the potential impact it could have on healthcare.
Demo Video
Project Journey
This project was completed over the course of 6 months. The first three months, the team focused on the requirements engineering portion of the project, where we set functional and non-functional requirements, created context and architecture diagrams and broke the project down with the stakeholders, so that it was easy for us to implement in the following 3 months, making sure we included the most important features and requirements. This process also allowed for the team to see how much is realistically achievable, and what should be kept as optional if time allowed us to complete.
For the implementation stage, the team utilised agile methodologies, sprints, continuous integration and continuous testing and git practices. Agile was the software development methodology chosen for this project as the team and stakeholders maintained constant communication; meetings every week, and we wanted continuous feedback on design and implementation. This way we were able to develop a successful product. At the start of the week, the team would update stakeholders on progress and decide what needs to be done before the next meeting. This would then be completed. We would also have our own internal meetings, to demonstrate work to other team mates and see how much progress has been made.
Technical Details
During the development process, the project team used a variety of software development tools and practices. Continuous integration processes were incorporated to support the reliability and scalability of the system. In particular, the project utilised advanced technologies such as Intel OpenVINO, which significantly improves the performance of the AI algorithms used within the system.
To build the GUI, Microsoft Foundation Classes (MFC) was utilised. All the data edites within the MFC application by staff will be saved within the database to ensure long-term storage of application data. There are many features including managing users, managing devices, managing signals and exporting data usage.
Triggers
In this section we show a visual representation of each trigger we have developed, as well as a video describing our project.
Tapping/Snapping Fingers Detection
The above gif demonstrates our sound classification trigger. It works by detecting these sounds repeatedly within a specified timeframe and then sending a signal to the WakeUp system. You can see in the above gif, the smart plug is turned on after a finger snapping is detected.
Eye Blinking Detection
As the gif demonstrates, our eye blinking detection triggers track the movement of the eye and constantly calculate the distance between upper and lower eyelids and count an eye blinking whenever the distance between eyelids is below the preset threshold. It counts the number of eye blinks over a certain period, with the count serving as a signal in the Wakeup System. For example, this trigger can be used for turning on lights or opening curtains.
Morse Code Vision
This gif shows our Morse code vision trigger. Based on the previous eye blinking trigger , we introduced a threshold to differentiate long and short blinking, allowing for Morse code communication. The gif shows after a long blink to initiate trigger, the three continuous short blinking has analysed to be the letter “S”. While a bit more complex for patients to use, it enables the transmission of letter signals compared to simple blinking detection, which allows the user to use at least 27 different actions for a single trigger. For example, a nurse can set up for the letter T to turn on the TV.
Fall Detection
This trigger detects if a patient is falling from a seated position by tracking upper body keypoints with the YOLOv8n-pose model, optimised with OpenVINO. A signal is generated if the patient’s body angle becomes too large, which can then prompt actions such as sending a message and photo to a nurse. The gif above showing the trigger constantly tracks the angle of the patient’s body and shows falling text when the patient’s body angle goes above the preset threshold.
Results and Outcomes:
OpenVino Benchmark:
As one of our key functional requirements, OpenVINO toolkit boost the inference performance of our triggers on edge devices, allowing us to run more capable models with limited computational power. To critically assess the performance boost provided by OpenVINO, we conducted a detailed benchmark on both triggers utilising OpenVINO, namely upper body fall detection and Whisper.
Upper Body Fall Detection
To assess the performance boost provided by OpenVINO, we conducted a benchmark for our upper body fall detection system. The system uses the YOLOv8n-pose model, comparing the performance with and without OpenVINO integration. We evaluated both live and offline inference performance. For live inference, we performed a continuous 3-minute test, while for offline inference, we assessed performance using the COCO 2017 validation dataset. Our comparisons focused on the mean boot time, pre-processing time, post-processing time, and inference time.
The benchmark was carried out on a computer running Ubuntu 22.04, equipped with an Intel i7-13650HX processor and 16GB of RAM.
The results, as depicted in the figures, reveal that despite OpenVINO slightly increased boot time and slightly improved on pre-processing and post-processing times, it made a huge improvement on the bottleneck of the model running time, which is average inference time. Notably, OpenVINO reduced the inference time by an average of 11 ms. Overall, including pre-processing and post-processing, the OpenVINO reduced the average latency by approximately 25%.
Whisper
To assess the performance boost provided by OpenVINO for Whisper, we conducted a benchmark for our audio transcript trigger, which utilises Whisper model. We evaluated both live and offline inference performance. The live benchmark included an hour of live inference, while for offline inference involved processing a 30-minute audio file. Our comparisons focused on the average inference time.
The improvements on Whisper model here are equally notable as for fall detection. For offline , OpenVINO cut the average inference time by 22%. And for live, we observed a remarkable 56% performance boost, with average inference time dropping from 1.2 seconds to just 0.5 seconds.
Evaluation of Wakeup System with Stakeholders and Professionals:
The WakeUp system has been evaluated through live, real-time demonstrations in front of two different audiences. The first demonstration took place during the FHIR Hackathon on February 2024, where we presented two signals. The first signal used blinking eyes as triggers to toggle a light bulb, while the second signal triggered an alert via Telegram when the user being monitored fell off a chair. These demonstrations were given to representatives from companies such as Roche, Microsoft and GOSH Drive.
The second demonstration took place during Labs Day on 19 March, where we demonstrated Morse Vision and Morse Sound to teams from Intel and to the CTO of NTT DATA.
All the live demonstrations went smoothly and there were no embarrassing glitches. All participants who tested the system were impressed and showed great interest in the product. They suggested various ideas on how this concept could be applied to other industries such as nuclear power plants, farms or theatres.
From the WakeUp team’s perspective, we would like the setup process to be simpler. For example, to add a trigger, you first have to register it with the WakeUp system and then share the credentials with the trigger. This could be streamlined if the trigger could automatically register itself, although this might compromise the security of our system.
We are also pleased at what started as an ‘exploratory’ project has quickly developed into an idea that has been presented to a real audience.
Lesson Learned:
Throughout the course of the project, we have been left with invaluable lessons about teamwork, communication and strategy. Some of the many lessons learnt include stakeholder and group communication, git practices and exposure to a variety of different technologies.
Stakeholder and group communication: As this project was in partnership with different stakeholders, we maintained continuous communication in order to produce a system which would best match their requirements. Weekly meetings would occur, where we would update stakeholders on progress and show what has been developed over the last week. As we used agile methodologies, we learnt that the requirements can change anytime during the project, and we should welcome the changes, as the focus is always on the stakeholder’s value. Communication is vital to ensure progress is made and it is very important to ensure all the voices of the stakeholder and team members are heard to be able to produce a successful product.
Git Practices: During this project, new concepts had been used such as squashing commits, git rebase, pull requests and git merge. Exposure to these concepts has further improved the knowledge of Git to us, and has given us the experience of professional git usage.
Exposure to different technologies: Over the duration, we worked with a range of technologies and concepts include Home Assistant, integration of Matter devices, machine learning integration, ZeroMQ and we also learnt how to build executable files. The exposure to all these technologies and new concepts has provided some professional programming practice, and as a result, improved the style of our code.
Collaboration and Teamwork
Team member contributions:
This project will be impossible without the collaboration between 9 of our amazing team members. The collaboration and teamwork has played a vital role in the success of this project. To ensure the smooth operation for our nine-person project, we have made a clear split of work between team members, which are shown below:
Frischer David Roman Louis (Team Leader): Team management, Stakeholder communication, development of Morse Vision and Morse Sound Trigger.
Hussain Fatima: Development of MFC front end, production of presentation video, development of WakeOnLan target.
Jakupov Dias: Development of sound based triggers, integration of OpenVINO with sound based triggers.
Kang Weihao: Development of Swagger documentation.
Rzayev Javid: Development of fall detection triggers.
Sivayoganathan Thuvaragan: Development of data statistics of WakeUp system.
Sun Ethan: Development of PyTest for continuous integration.
Wang Jingyuan: Development of Eye blinking trigger, integration of OpenVINO with vision based trigger, production of presentation video.
Wang Zena: Production of MFC front end.
Project Management
To ensure the smooth operation of our nine-person project, we have established a rigorous methodology and set of rules for project management and teamwork.
Throughout the 10 weeks of development, we held three weekly meetings to maintain the ongoing progress of the project. Meetings with our UCL supervisors were scheduled for Mondays, internal meetings to organise the weekly tasks took place on Wednesdays, and update meetings with our Intel partner were held on Fridays.
Each member of the WakeUp Team had a specific role to fulfill, with the Team Leader (TL) assisting and ensuring that everyone completed their tasks on schedule. To promote collaboration and integration among team members, strict common practices were implemented. For example:
Commit Message: Must follow this template: [Subject] Description of the task achieved. Following this convention made it easier to track the progress of each component in our mono-repository on GitHub.
Pull Request review: Only the TL was authorised to push to the main branch. Other members were required to create a pull request, where one or two members would review it to ensure that the commit message followed convention, that there was a single commit (squash) to be rebased and merged into main, and that the commit had passed the project’s pytest to ensure that it would not break other components of the system.
Notion App: The TL motivated all team members to document their work progress and knowledge gained throughout the project in the Notion workspace. Information about organisation, setup guides, troubleshooting, and learning was recorded on the Notion page to centralise the team’s knowledge.
Future Development
The Matter WakeUp Signal System holds significant promise for future development and enhancements. Here are some potential areas for improvement:
Simplified Setup and Installation
Introducing a graphical installation process would make it easier for non-technical users to configure and use the system. This would streamline the setup process, reducing the potential for errors and making the system more accessible.
Advanced and Varied Triggers
Integrating more advanced machine learning models for precise patient monitoring and interaction could enhance the system’s capabilities. This includes expanding the range of triggers to accommodate various patient needs and conditions.
Broader Device Compatibility
Expanding the range of compatible smart devices and ensuring seamless integration with other healthcare systems and standards is crucial. Future testing should include a wider array of smart devices like smart speakers and additional sensors.
Conclusion
The Matter WakeUp Signal System project demonstrates the transformative potential of integrating smart technology into healthcare settings. Here are the key points:
Patient Autonomy: By enabling patients with disabilities and the elderly to control their environment autonomously, the system significantly improves their quality of life.
Workload Reduction: The system reduces the workload on nurses and hospital stuff by automating routine tasks and monitoring.
Innovative Approach: The successful implementation of various triggers, the integration of Matter devices, and the use of advanced AI technologies like OpenVINO showcase the project’s innovative approach.
Positive Feedback: The system has received positive feedback from stakeholders and has shown practical applications and potential impact through successful demonstrations.
The project’s commitment to enhancing patient autonomy and improving healthcare efficiency makes it a valuable addition to the field of healthcare technology.
Special Thanks to Contributors:
Each contributor’s continuous support and involvement all plays a crucial role in the success of the project, here, we present a special thanks to all following contributors.
Prof. Dean Mohamedally, Chief Supervisor and Professor of Computer Science at UCL
Emmanuel Letier, Associate Professor in Software Engineering at UCL
Costas Stylianou, Senior Technical Specialist for Public Sector and Health & Life Sciences at Intel, and Honorary Associate Professor at UCL
Prof. Julia Manning, Professor, Clinician, Policy Adviser, Convenor
Dr. Rafiq, NHS GP / GP Trainer / Honorary Lecturer
Anelia Gaydardzhieva, Assistant Supervisor at UCL
Jason Holtom, Account Executive for the Public Sector and Healthcare
Call to Action
We invite you to explore the Matter WakeUp Signal System further and consider how its innovative approach to patient care can be applied in your own healthcare settings. Here are some steps you can take:
Connect with Us: Feel free to reach out to our team for more information or collaboration opportunities. Together, we can continue to innovate and improve the quality of care for patients.
Team
The team involved in developing this project included 9 members. All of us are Masters students at UCL studying Software Systems Engineering:
David Frischer – Team Leader – Full Stack Developer.
GitHub URL: https://github.com/davidfrisch,
LinkedIn URL: https://www.linkedin.com/in/david-frischer/
Fatima Hussain – Full Stack Developer.
GitHub URL: https://github.com/fatimahuss,
LinkedIn URL: https://www.linkedin.com/in/fatima-noor-hussain/
Dias Jakupov – Full Stack Developer.
GitHub URL: https://github.com/Dias2406/,
LinkedIn URL: https://www.linkedin.com/in/dias-jakupov-a05258221/
Jingyuan Wang – Full Stack Developer.
GitHub URL: https://github.com/Andydiantu,
LinkedIn URL: https://www.linkedin.com/in/jingyuan-wang-9ba553208/
Weihao Kang – Full Stack Developer.
GitHub URL: https://github.com/Kang2001,
LinkedIn URL: https://www.linkedin.com/in/weihao-kang-b25152294
Thuvaragan Sivayoganathan – Full Stack Developer.
GitHub URL: https://github.com/thuvasiva,
LinkedIn URL: https://www.linkedin.com/in/thuvaragan-sivayoganathan-a95991227/
Javid Rzayev – Full Stack Developer.
GitHub URL: https://github.com/Javid2002,
LinkedIn URL: https://www.linkedin.com/in/javidrzayev/
Ethan Sun – Full Stack Developer.
GitHub URL: https://github.com/EthanSun11
Zena Wang – Full Stack Developer.
GitHub URL: https://github.com/ZenaWangqwq
#Accessibility #Innovation #SmartHome #TechnologyForGood #Matter #HomeAssistant #Micrososft #Intel #UCL #IXN
Microsoft Tech Community – Latest Blogs –Read More
Wide Community Reach at Modern Workplace Conference Paris
The Modern Workplace Conference Paris 2024, primarily aimed at French-speaking users, has been held. In its sixth edition, the conference featured various speakers, including Microsoft MVPs, Regional Directors, industry technology experts, and Microsoft employees. They delivered more than 75 sessions over two days, providing attendees with the latest technical information on Microsoft 365, Power Platform, including Microsoft AI and Copilot.
In this blog, we introduce the insights and future community activities of two MVPs who contributed significantly to the success of this conference.
Microsoft MVP, Chloé Moreau, describes her own role at the conference as “a big project manager or a conductor,” working alongside talented MVPs and passionate community leaders to ensure the best planning and execution. Although they are highly motivated community leaders rather than professional event organizers, they tackled challenges head-on and were proud of delivering a high-quality event. “Our best asset is that we are passionate people loving to share content and knowledge on our preferred technologies, for MWCP it is Microsoft 365 and Power Platform,” says Chloé.
Two years ago, the fourth event was held entirely online due to the limitations of pandemic, which over the following years, transformed into a hybrid format. Hybrid events enable extensive information sharing about new technologies not only to on-site attendees but also to remote participants. However, managing multiple communication channels makes the operation more complex. For this event, in addition to the on-site venue, organizer members managed live streaming on YouTube and used Teams for sharing slides and facilitating participant interaction. Reflecting on these efforts, Chloé states, “We were able to offer a great quality of interactions both online and in person by really proving all hybrid options to our attendees.”
Regarding concerns that offering more participation options might reduce the number of people attending in person, Chloé mentions, “This year we had a very strong level of attendees participating in person despite all content being accessible on YouTube. So, we are convinced that hybrid is the way to go for the future as Microsoft showed this for Microsoft Ignite for example.”
Chloé expresses a strong desire to continue supporting community members through various online channels. In addition to sharing the latest Microsoft news on LinkedIn, Facebook, X, and Instagram, the community hosts groups with over 6,500 professionals worldwide, monthly podcasts, and various community events that have attracted over 10,000 participants across five continents in the past eight years. By continuously supporting participants who meet at events, community leaders continue to demonstrate exemplary leadership that contributes to the growth of both individuals and the community as a whole.
Another key organizer, Patrick Guimonet, also an MVP, played a significant role in coordinating numerous aspects of the event from planning to execution, greatly contributing to its success. He expresses his joy, saying, “I am very proud to contribute to the success of this event and to be part of such a passionate, motivated, and committed team. Each edition is a new adventure that allows us to unite people and share our passion.”
Through interactions with participants, Patrick learned the importance of session diversity and innovation. He discovered that participants are not just looking for various presentations but are interested in practical case studies that provide specific knowledge. This feedback, offering practical insights into both business and technical challenges, was highly valuable.
Like Chloé, Patrick also reflects on the hybrid nature of the event, emphasizing that the YouTube session videos met participant expectations, stating, “This flexibility allows them to review sessions at their leisure, catch up on any content they might have missed, or simply refresh their memory on the information presented.”
Looking ahead to future community activities, Patrick mentioned the regular events hosted by aMP (formerly aMS) community. These events offer opportunities for direct interaction at local events and include online streaming, allowing participation regardless of location. They provide a great hybrid event experience where the community can learn about the latest updates of Microsoft 365, Power Platform, and more. Community events are planned in various cities worldwide, so we encourage you to join these events.
– June 25, 2024: aMS Brazzaville
– August 1, 2024: aMP Colombo
– August 24, 2024: aMP Pune
– August 27, 2024: aMP Salem
– September 12, 2024: aMP Tunis
– September 19, 2024: aMP Bordeaux
– September 27, 2024: aMS Leipzig
– October 3, 2024: aMP Montpellier
– October 18, 2024: aMP Seoul
– October 23, 2024: aMP Kuala Lumpur
– October 25, 2024: aMP Manila
Microsoft Tech Community – Latest Blogs –Read More
How to do fast fourier analysis of first harmonic in matlab?
In simulink there is a block called, Fast Fourier Analysis, that given the fundamental frequency it extracts the phase delay and the magnitude amplification. I need to do the same thing in matlab, how can i do it? The harmonics of which I would like to extract the information it is just the first one. Is there a function or a specific code that i can use?
The data signal would then be given as input as an array with the relative time.In simulink there is a block called, Fast Fourier Analysis, that given the fundamental frequency it extracts the phase delay and the magnitude amplification. I need to do the same thing in matlab, how can i do it? The harmonics of which I would like to extract the information it is just the first one. Is there a function or a specific code that i can use?
The data signal would then be given as input as an array with the relative time. In simulink there is a block called, Fast Fourier Analysis, that given the fundamental frequency it extracts the phase delay and the magnitude amplification. I need to do the same thing in matlab, how can i do it? The harmonics of which I would like to extract the information it is just the first one. Is there a function or a specific code that i can use?
The data signal would then be given as input as an array with the relative time. matlab, signal, fft, signal processing, digital signal processing, frequency, simulink MATLAB Answers — New Questions
How to add a customized drive cycle in the vehicle composer app?
I want to add a customized drive cycle in the vehicle composer app. How can I add it to the app?I want to add a customized drive cycle in the vehicle composer app. How can I add it to the app? I want to add a customized drive cycle in the vehicle composer app. How can I add it to the app? vehicle composer app, matlab, drive cycle MATLAB Answers — New Questions