Problem 1. For the following MIPS assembly instructions above, what is a corresp

Problem 1. For the following MIPS assembly instructions above, what is a corresponding C statement?
add f, g, h
add f, i, fProblem 2. For the following C statement, what is the corresponding MIPS assembly code? Assume that the variables f, g, h, i, and j are assigned to registers $s0, $s1, $s2, $s3, and $s4, respectively. Assume that the base address of the arrays A and B are in registers $s6 and $s7, respectively.
B[8] = A[i−j]Problem 3. Translate 0xabcdef12 into decimal. You may simply assume that it is an unsigned integer.
Problem 4. Assume $t0 holds the value 0x00101000. What is the value of $t2 after the following instructions?
slt $t2, $0, $t0
bne $t2, $0, ELSE
j DONE
ELSE: addi $t2, $t2, 2
DONE:Problem 5. What decimal number does the bit pattern 0x0C000000 represent if it is a floating point number? Use the IEEE 754 standard. Explain in detail how you get your answer.
=============
Linked Lists
You have been provided the code for doubly linked list: doubly_linked_list.py. Using this code, perform the following tasks:
An interesting use-case of a linked list is to track edits in a “Undo – Redo” interface. Thus far we have really only talked about connecting singular data points in the nodes. The following task will deviate from that:
I want you to create an interface of an application that will alter the contents of a list. As you alter the contents of the list, you should be able to retrieve the previous state of the list as you change it, much like being able to undo and redo changes in a
document. Your application interface should support three basic functions, undo(), redo(), and do() where “do()” is what actually alters the contents of the list. You can interpret “do()” as what happens when you type in a word processor. I want you to
“do()” the following actions:
Create a list with the initial values of: [5,3,2,1,4,8]
Sort the list.
Reverse the list
Add a 9 to the end of the list.
Undo back to before you reversed the list.
Add a 9 to the end of the list again
Undo back to the original state of the list.
After every operation, print the current state of the “application”, remember that your application’s only functionality is to change the state of the list.
Stacks
Using a linked structure (doubly, or singly linked list) create a stack structure. From this structure (the stack) and the included text file palindrome.txt, determine which of the words within the file are proper palindromes. Your solution must utilize the stack
structure. However, You may use other tools/functions within the language of your choice to check your work.
Queues
Finally, this last section is not a coding challenge.
A remote printing system serving a large pool of individuals can be very complicated to support. In theory, a simple queue that takes in print requests and dequeue’s them once they have been processed would serve all the required operations. However, there
are significant problems that arise as far as user requests and other things. What are some of the issues that you can see with a simple queue that only supports First In First Out operations typical of a queue? (Enqueue, dequeue, peek, etc.) For your submission,
you can either submit a second video of 1-2 minutes in length, or small report of approximately 1 page that discusses the various shortcomings of a queue to support a remote printer system.
Your submission should be accompanied by a 8 minute walk-through of your code. This analysis should include your decision making process, the logic behind you code, an your original thoughts that went into the decision making on why your code is written
and performs in the manner in which you have written it. If you can not adequately explain how your code functions, it is difficult to believe that you created it yourself as it is inherently difficult to make that which you don’t understand.
All video submissions must:
Be narrated by your own voice – Silent submissions will not be considered
If you need accommodations regarding your voice recording, reach out to me
BEFORE
the due date of the assignment
Capture your screen to include the source code and other assets required by the assignment if necessary for the comprehension of your explanation.
Your submission should include:
A link to your YouTube/Loom Video upload submitted as a .txt file or as a submission comment
OR
a video file (.mp4 preferred).
AND
Your code project (source code, resource files, etc.) unzipped.
If necessary, provide a README file if an explanation is required to execute your code.

Dear Students, As for assignment 3, you have to re-implement the following paper

Dear Students,
As for assignment 3, you have to re-implement the following paper Features Extraction part only as we discussed in class.
You can download the paper using the following URL:
https://library.imaging.org/admin/apis/public/api/ist/website/downloadArticle/jist/63/2/art00004
You are free to use any programming language (Python, Matlab etc.).
You can download the sample images using the following link:
https://sourceforge.net/projects/pmu-ud/
PMU-UDDownload PMU-UD for free. handwritten dataset of Urdu/Arabic Numerals. The handwritten dataset was collected from 170 participants with a total of 5,180 numeral patterns. The dataset is named Prince Mohammad Bin Fahd University – Urdu/Arabic Database (PMU-UD).SourceForge
You need to submit the working code along with the output CSV File.

Deliverables Deliverable 1: Create Accounts table and setup Sub-Task 1: Add a

Deliverables
Deliverable 1: Create Accounts table and setup
Sub-Task 1: Add a screenshot from the db of the system user (Users table)

(Clearly show/caption which is the system user (should not be a real user, password should not be a valid password/hash))

Sub-Task 2: Add a screenshot from the db of the world account (Accounts table)
(Clearly show/caption which is the world account (should have account number 000000000000, should be of type world, should be associated with the system user))

Sub-Task 3: Explain the purpose and usage of these two entries and how they relate
(explain why they’re needed for transactions)

Deliverable 2: Dashboard

Sub-Task 1: Add a screenshot showing the requested links/navigation

Links in the navbar don’t count (it’s ok if some are duplicated here and navbar). Ensure the screenshot shows the heroku dev url
Deliverable 3: Create a checking Account

Sub-Task 1: Add a screenshot showing the Create Account Page. (Have valid date filled in) (Ensure the screenshot shows the heroku dev URL)

Sub-Task 2: Add screenshots showing validation errors and success message. (Show the minimum funding validation) (Show the success message from task 1’s data) (Ensure the screenshot shows the heroku dev URL)

Sub-Task 3: Add a screenshot showing the transaction generated from the initial deposit (from the DB) (Clearly highlight or mention in the caption which to look at. There should be two records showing the positive and negative movement of funds between accounts)

Sub-Task 4: Explain which account number generation you used and the account creation process including the transaction logic. (Clearly mention the option number and the text from the proposal).( Clearly explain the full steps of creating an account including the association to the user and the transactions being generated (at a high level as they’re discussed in detail later))
Deliverable 4: User will be able to list their accountsSub-Task 1: Add a screenshot showing the user’s account list view (show 5 accounts) (There should be at least 5) (Show account number, account type, modified, and balance)(Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Briefly explain how the page is displayed and the data lookup occurs (Explain the database call and the data used to get the data and how it’s displayed on the webpage)
Deliverable 5: Account Transaction Details
Sub-Task 1: Add a screenshot of an account’s transaction history.(should have at least a few samples)(Account: Show account number, account type, balance, opened/created date of the selected account (from Accounts table))(Transactions: Show the src/dest account numbers (not account id), the transaction type, the change in balance, when it occurred, expected total, and the memo) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Explain how the lookup and display occurs (Describe the db query and the data used to fetch the necessary results and anything else relevant)
Deliverable 6: Deposit/Withdraw
Sub-Task 1: Show a Screenshot of the Deposit Page (Show valid data filled in) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Show a Screenshot of the Withdraw Page (this potentially can be the same page with different views)(Ensure the screenshot shows the heroku dev URL) (Page should include a dropdown of logged in user’s accounts and a text field to add desired amount to)
Sub-Task 3: Show validation error for negative numbers (Ensure the screenshot shows the heroku dev URL)

Sub-Task 4: Show validation error for withdrawing more than the account contains(Ensure the screenshot shows the heroku dev URL)

Sub-Task 5: Show a success message for deposit and withdraw (2 screenshots) (Shows deposit success)(Shows withdraw success)
Sub-Task 6: Show a screenshot of the transaction pairs in the DB for the above tests (Expected total should be accurate for both accounts)(Highlight or mention in caption which records to look at)

Sub-Task 7: Briefly explain how transactions work (List each step and give some detail on it: Should include account lookup, expected total calculation, two transaction records, and updating the account balances based on the history (not basic math))

Deliverables Deliverable 1: Create Accounts table and setup Sub-Task 1: Add a

Deliverables
Deliverable 1: Create Accounts table and setup
Sub-Task 1: Add a screenshot from the db of the system user (Users table)

(Clearly show/caption which is the system user (should not be a real user, password should not be a valid password/hash))

Sub-Task 2: Add a screenshot from the db of the world account (Accounts table)
(Clearly show/caption which is the world account (should have account number 000000000000, should be of type world, should be associated with the system user))

Sub-Task 3: Explain the purpose and usage of these two entries and how they relate
(explain why they’re needed for transactions)

Deliverable 2: Dashboard

Sub-Task 1: Add a screenshot showing the requested links/navigation

Links in the navbar don’t count (it’s ok if some are duplicated here and navbar). Ensure the screenshot shows the heroku dev url
Deliverable 3: Create a checking Account

Sub-Task 1: Add a screenshot showing the Create Account Page. (Have valid date filled in) (Ensure the screenshot shows the heroku dev URL)

Sub-Task 2: Add screenshots showing validation errors and success message. (Show the minimum funding validation) (Show the success message from task 1’s data) (Ensure the screenshot shows the heroku dev URL)

Sub-Task 3: Add a screenshot showing the transaction generated from the initial deposit (from the DB) (Clearly highlight or mention in the caption which to look at. There should be two records showing the positive and negative movement of funds between accounts)

Sub-Task 4: Explain which account number generation you used and the account creation process including the transaction logic. (Clearly mention the option number and the text from the proposal).( Clearly explain the full steps of creating an account including the association to the user and the transactions being generated (at a high level as they’re discussed in detail later))
Deliverable 4: User will be able to list their accountsSub-Task 1: Add a screenshot showing the user’s account list view (show 5 accounts) (There should be at least 5) (Show account number, account type, modified, and balance)(Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Briefly explain how the page is displayed and the data lookup occurs (Explain the database call and the data used to get the data and how it’s displayed on the webpage)
Deliverable 5: Account Transaction Details
Sub-Task 1: Add a screenshot of an account’s transaction history.(should have at least a few samples)(Account: Show account number, account type, balance, opened/created date of the selected account (from Accounts table))(Transactions: Show the src/dest account numbers (not account id), the transaction type, the change in balance, when it occurred, expected total, and the memo) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Explain how the lookup and display occurs (Describe the db query and the data used to fetch the necessary results and anything else relevant)
Deliverable 6: Deposit/Withdraw
Sub-Task 1: Show a Screenshot of the Deposit Page (Show valid data filled in) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Show a Screenshot of the Withdraw Page (this potentially can be the same page with different views)(Ensure the screenshot shows the heroku dev URL) (Page should include a dropdown of logged in user’s accounts and a text field to add desired amount to)
Sub-Task 3: Show validation error for negative numbers (Ensure the screenshot shows the heroku dev URL)

Sub-Task 4: Show validation error for withdrawing more than the account contains(Ensure the screenshot shows the heroku dev URL)

Sub-Task 5: Show a success message for deposit and withdraw (2 screenshots) (Shows deposit success)(Shows withdraw success)
Sub-Task 6: Show a screenshot of the transaction pairs in the DB for the above tests (Expected total should be accurate for both accounts)(Highlight or mention in caption which records to look at)

Sub-Task 7: Briefly explain how transactions work (List each step and give some detail on it: Should include account lookup, expected total calculation, two transaction records, and updating the account balances based on the history (not basic math))

Deliverables Deliverable 1: Create Accounts table and setup Sub-Task 1: Add a s

Deliverables
Deliverable 1: Create Accounts table and setup
Sub-Task 1: Add a screenshot from the db of the system user (Users table)
(Clearly show/caption which is the system user (should not be a real user, password should not be a valid password/hash))
Sub-Task 2: Add a screenshot from the db of the world account (Accounts table)
(Clearly show/caption which is the world account (should have account number 000000000000, should be of type world, should be associated with the system user))
Sub-Task 3: Explain the purpose and usage of these two entries and how they relate
(explain why they’re needed for transactions)
Deliverable 2: Dashboard
Sub-Task 1: Add a screenshot showing the requested links/navigation
Links in the navbar don’t count (it’s ok if some are duplicated here and navbar). Ensure the screenshot shows the heroku dev url
Deliverable 3: Create a checking Account
Sub-Task 1: Add a screenshot showing the Create Account Page. (Have valid date filled in) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Add screenshots showing validation errors and success message. (Show the minimum funding validation) (Show the success message from task 1’s data) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 3: Add a screenshot showing the transaction generated from the initial deposit (from the DB) (Clearly highlight or mention in the caption which to look at. There should be two records showing the positive and negative movement of funds between accounts)
Sub-Task 4: Explain which account number generation you used and the account creation process including the transaction logic. (Clearly mention the option number and the text from the proposal).( Clearly explain the full steps of creating an account including the association to the user and the transactions being generated (at a high level as they’re discussed in detail later))
Deliverable 4: User will be able to list their accountsSub-Task 1: Add a screenshot showing the user’s account list view (show 5 accounts) (There should be at least 5) (Show account number, account type, modified, and balance)(Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Briefly explain how the page is displayed and the data lookup occurs (Explain the database call and the data used to get the data and how it’s displayed on the webpage)
Deliverable 5: Account Transaction Details
Sub-Task 1: Add a screenshot of an account’s transaction history.(should have at least a few samples)(Account: Show account number, account type, balance, opened/created date of the selected account (from Accounts table))(Transactions: Show the src/dest account numbers (not account id), the transaction type, the change in balance, when it occurred, expected total, and the memo) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Explain how the lookup and display occurs (Describe the db query and the data used to fetch the necessary results and anything else relevant)
Deliverable 6: Deposit/Withdraw
Sub-Task 1: Show a Screenshot of the Deposit Page (Show valid data filled in) (Ensure the screenshot shows the heroku dev URL)
Sub-Task 2: Show a Screenshot of the Withdraw Page (this potentially can be the same page with different views)(Ensure the screenshot shows the heroku dev URL) (Page should include a dropdown of logged in user’s accounts and a text field to add desired amount to)
Sub-Task 3: Show validation error for negative numbers (Ensure the screenshot shows the heroku dev URL)
Sub-Task 4: Show validation error for withdrawing more than the account contains(Ensure the screenshot shows the heroku dev URL)
Sub-Task 5: Show a success message for deposit and withdraw (2 screenshots) (Shows deposit success)(Shows withdraw success)
Sub-Task 6: Show a screenshot of the transaction pairs in the DB for the above tests (Expected total should be accurate for both accounts)(Highlight or mention in caption which records to look at)
Sub-Task 7: Briefly explain how transactions work (List each step and give some detail on it: Should include account lookup, expected total calculation, two transaction records, and updating the account balances based on the history (not basic math))

Dice simulator: – Create a six and eight-sided dice simulator (8 points). – Plea

Dice simulator:
– Create a six and eight-sided dice simulator (8 points).
– Please make sure that it is a FAIR die.
– Cover it with a simple, easy to use GUI (8 points).
– please provide a good, clean comments (carry 4 points)
Submission Requirement:
1. need the ipynb file
2. can run in Jupyter Notebook
thank you! please feel free to ask any further detailde requirements about this.I have already done the code for rolling dice without the Gui part it’s what you’ll need to do bellow is the code
import random
def rolldice(min,max):
while True:
print(“roll the dice…”)
print(f”Your number after roll is:{random.randint(min,max)}”)
input(“do you want to roll dice again? enter y for yes and n for no”)
if choice.lower()==’n’:
break
rolldice(1,6)
DO WHATEVER IS MISSING AND WHATEVER YOU WANT BUT I NEED SOMETHING RUNNING AND A GOOD GUI FOR HAVING A GOOD GRADE