Question about Finite State Automatons

  • Thread starter Thread starter Wallboy
  • Start date Start date
  • Tags Tags
    Finite State
AI Thread Summary
The discussion revolves around the limitations of finite state automata (FSA) in recognizing certain languages, specifically the language {0n1n | n ≥ 0}, which an FSA cannot handle. A participant suggests using a counter associated with the states to track the number of 0s seen, allowing the machine to determine how many 1s to output when transitioning states. However, this approach raises concerns about the counter's capacity, as it would need to accommodate an infinite range of n values. The conversation highlights the theoretical constraints of FSAs, emphasizing that while practical counters can be designed for large values, they cannot address the infinite nature of the problem, ultimately reaffirming the fundamental limitations of FSAs in automata theory.
Wallboy
Messages
4
Reaction score
0
I'm reading about automata theory and am currently at the part about what a FSA can recognize and what it cannot. They use the example of some language: {0n1n | n ≥ 0} which an FSA cannot be built for.

When I first started learning about state machines before reading into theory of computation was from the Mealy/Moore models where we can have outputs associated with each state.

So my question is, could you not have an output associated with the first state such that every time it would see a 0, an output signal would be generated to increment some external counter, so that when the machine finally does see a 1, it jumps to the next state and uses that counter information to know how many 1's to repeat?

I'm guessing I am jumping ahead and adding more power to the 5-tuple description of what a FSA really is?
 
Technology news on Phys.org
Wallboy said:
So my question is, could you not have an output associated with the first state such that every time it would see a 0, an output signal would be generated to increment some external counter, so that when the machine finally does see a 1, it jumps to the next state and uses that counter information to know how many 1's to repeat?

What do you do when the counter overflows? Your idea works up to the maximum number the counter can hold, but it doesn't solve the problem for ANY value of n.

You could easily make a counter big enough for any practical purpose (e.g. it would work if the number of 0s and 1s was as big as the number of atoms in the observable universe) but the question is about the theoretical situation when there is no limit to the size of n.
 
Ahh that's right. I just over thought it and forgot that the counter itself would have to go to infinity. Thanks.
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
Thread 'Project Documentation'
Trying to package up a small bank account manager project that I have been tempering on for a while. One that is certainly worth something to me. Although I have created methods to whip up quick documents with all fields and properties. I would like something better to reference in order to express the mechanical functions. It is unclear to me about any standardized format for code documentation that exists. I have tried object orientated diagrams with shapes to try and express the...
Back
Top