I make a simulation model for recycling.
There is no problem with the model for the user, but a problem occurs in the process of collecting by the truck.
If the recovery box is full, the truck starts, but the truck goes to the wrong place instead of going to the full place.
How can I independently recognize the recovery box and send the truck to the full recovery box?
please solve this..
The link below is my model image.
Thanks.
Related
I'm trying to make an scenario in OMNeT with different Areas. Each area is a compound module which have many nodes inside, such like a city or something like that. I want that nodes moves from one area to another.
I already done that, but the nodes that are dynamically inserted in their new areas throws error when they are going to perform a transmission.
The error is not throwed in all transmissions, just sometimes.
I debugged my code and the error is in Signal.cc file, seems that node doesn't find the radioMediumModule. I'm using IEE802.15.4 communications and SensorNode module.
I think thay maybe is an allocation of memory problem, since the error does not always throw.
Thanks in advance.
Im very new to Tm1 and have to implement a new function in my code.
Is there any way to undo your last action?
For better understanding ill write an example:
I have 8 different cubes and i will upload one after one.
If one cube is not able to be uploaded all the others shouldnt be uploaded too.
Every cube which is already being uploaded should get a reset to the previous state.
Is there a way to implement it?
You have to inbriquate your 8 loading process in a master (others are slaves). If you have a condition that make one or your cube unuploadable you use the ProcessError function. In the master process, you fetch the result of the execution of each slave process. If one is in error, you use the processerror function (in the master). All the chain won't be commited.
The answer above from Wuzardor provides an approach using TI processes but your question seems to suggest you're using TM1py/Python to do the upload to TM1, either directly, or by triggering TI processes through the REST API.
In general, there's no easy way to roll back changes to cube data. However, it should be simple enough to structure your Python code such that the existence and validity of all the load files is established before you push anything to any of your cubes. It's difficult to suggest the best approach without more details about what you're trying to achieve and how.
Updated in response to OP comment:
OK, while it's not clear what IT isn't cooperating with, but if you are unable to verify the source prior to extracting it, you can always load it first to a staging cube, where the data can be checked, before copying anything to your main cubes. Depending on what issues you tend to face with the data, you might be able to automate this check or might need to rely on a human looking at it. Either way, just don´t overwrite your historic data until you've checked the new data.
Furthermore, you might want to think about your overall design. Might it make sense to retain a copy of the previous data in the cubes anyway? Why not build your cubes such that you can keep the history, rather than re-overwriting each time? Finding a sensible design really depends on the details of your application but you might benefit from looking at it with fresh eyes.
Cheers
Alex
I have several agents.In each agent, I've made a state chart. Some states overlap with other states from other agents. With my simulation I want to show in which state an agent is currently in.
Is it possible to show all statecharts at the same time (during execution)? For example via viewArea?I only find examples in the AnylogicHelp if the statecharts are already in the main, but not if they are in the agents.
I am happy about every answer and thank you very much.
NEW
Thank you for your quick response.
I have formulated my question unclearly. I know your suggested solution from "AnyLogic in three days" or "The big book of simulation modeling". My point is that I want to display the statecharts of all agents side by side in the Main. I can't just drag these statecharts into the main, because some codes don't work anymore.
So I have several different agents with certain properties (parameters etc.). In each agent I have created a statechart. One of my subgoals is to show the processes of all agents at the same time by statecharts (in the Main). I want to see where an agent is in which state during the simulation execution.
During the execution you can display a statechart by selecting an agent, see inserted figure. I want to display all statecharts at the same time in the main, but in a way that they remain in the respective agent.
Excuse me...my English is not that good.
Thank you very much. :)
Typically, you animate some part of each of your agents to reflect their state. Use a rectangle for example. Then, in each state "OnEnter" code box, change its color using ' rectangle.setFillColor(red)'.
Now, each agent will be visible on Main (if you embedded them properly) and you get a visual indication of their state.
Lots of example models do this as well, check them out:)
Below is a general ETL flow chart diagram.I am really confused if it is a good practice to draw such a flow chart.Especially at lines connecting the final output , and the big box used to generalize the whole process that goes from input format to 'Validate files as per type of file' to 'Adjustments for desired output' and finally to 'outputs'.
In concept, to provide an overview of the process, a Context diagram or Data Flow Diagram can be used as well as a Flow Chart. While all these diagrams are old, they are usually useful.
I suggest that you check the following points in your diagram - What I have here are personal suggestions based on long history with ETL.
Your processing shape (say rectangle) must have at least one entry (input) and at least one exist(output). Example: The two large rectangles don't have clear inputs and outputs! What is going on there?
You can't have outputs without a process - Example: Type 1 is somehow split into Type 1.1 and Type 1.2. How is that split happened? Is it by a program? Which one? Another example is Type 1.1 has an arrow connected to Output 1. Again same questions hold. Another example is "Rejected folder" to email.
The name of the process should indicate what the process is or the actual program component name or physical file names. This is valuable in ETL.
You may want to show the process triggering event such as time of day.
Use remarks.
Make the level of detail consistent.
I'm very new to settop box project.Is there any materials available to study the basics of its internals and the working of it.I dont know how to start understand about it.I was looking for the architecture of middleware,DCCM and other components.I need to know how these components interact with each other.I need to know how by pressing a particular event in the EPG menu we could able to get the event corresponding to the service.I need to know the interaction between the tables.How to set the reminder in EPG and how the interactive TV works.
This is only a very partial answer to your question. Rather i would say, this is the first preliminary work you must accomplish before getting deeper into interactivity.
The tutorial here on PSIP: Program specific information show how the ATSC (or DVB is similar) is organized in the form of periodic tables including some tables that indicate EPG. By reading and processing such tables you will be able to accomplish the desired work.
Essentially, EPG table contains the information about the program and its respective time. And the actual timing information is contained in the TDT and TOT table. These tables tells the STB's the current time (on wall clock). Once, the respective time occurs, as per the TDT/TOT, the notification action can fire.
Below here are two more important references to Transport stream structures.
PSIP tutorial
The ATSC transport layer, including program and system information protocol (PSIP)
Please read the above pre-requsite and then refine your question.